[SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

amartin · 2015-02-04 04:17:03

I recently upgraded from KDE 4.12 to Plasma 5.2 following the instructions in this thread. The upgrade went smoothly and I was able to login and use the new Plasma 5 desktop successfully for a couple of days. However, today on boot and login (using sddm), the KDE loading screen is displayed and the progress bar gets to 100%, but the plasma desktop never loads.

It appears that plasma is running (in some capacity), because if I let it sit for awhile it will display the KDE lock screen and even let me "unlock" the session, which brings me back to the loading screen. If I create a new user from the command line, I am able to login successfully as this new user. I tried removing my ~/.kde4 and some other config files from my existing profile with no improvement in behavior.

What else can I try to resolve this problem with Plasma 5?

Thanks!

Last edited by amartin (2015-02-06 02:38:12)

arojas · 2015-02-04 07:48:40

Try removing all plasma* files and dirs from .config and .cache

amartin · 2015-02-04 13:57:39

I gave that a try but no change in behavior. Any other ideas?

Head_on_a_Stick · 2015-02-04 14:04:17

Have you selected "plasma" in the SDDM login screen?

amartin · 2015-02-04 14:40:15

Yes, I also tried invoking plasmashell manually from another TTY (via export DISPLAY=:0.0 && /usr/bin/plasmashell --shut-up) but no luck. Note that the new user I created can login to "plasma" from sddm without issue

mauritiusdadd · 2015-02-04 15:14:55

Hi amartin,
Are you using any third-party plasma widget?
can you post the content of your ~/.xsession-errors just after a reboot and (failed) login?
It may be useful to check also the journal for errors:

journalctl -b | egrep "[Ee][Rr][Rr]"

amartin · 2015-02-05 03:03:04

Hi mauritiusdadd,

I am not using any third-party plasma widgets. Here's the contents of ~/.xsession-errors:

/etc/locale.conf: line 1: en_US.UTF-8: command not found
startkde: Starting up...
kbuildsycoca5 running...
Baloo File Indexing has been disabled
Already running
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(640) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(640) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(640) kdemain: Emitting notifyDatabaseChanged ()
requisition.width, requisition.height = self.__child.size_request ()
requisition.width, requisition.height = self.__child.size_request ()
gtk.main()
gtk.main()
kio_file(674) kdemain: Starting 674
kio_file(676) kdemain: Starting 676
kio_file(677) kdemain: Starting 677
kio_file(678) kdemain: Starting 678
dolphin(562) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
Service started, version: 6.2.0
Service started, version: 6.2.0

Also, here's the errors in "journalctl -b":

Feb 04 20:00:59 hostname colord[342]: (colord:342): Cd-WARNING **: failed to get session [pid 321]: Unknown error -2
Feb 04 20:00:59 hostname colord[342]: /usr/lib/colord/colord-sane: error while loading shared libraries: libsane.so.1: cannot open shared object file: No such file or directory
Feb 04 20:03:35 hostname kdeinit5[468]: Qt: Session management error: networkIdsList argument is NULL
Feb 04 20:03:36 hostname kdeinit5[470]: Qt: Session management error: networkIdsList argument is NULL
Feb 04 20:03:39 hostname kdeinit5[485]: Qt: Session management error: networkIdsList argument is NULL
Feb 04 20:03:43 hostname kscreen_backend_launcher[521]: Qt: Session management error: networkIdsList argument is NULL
Feb 04 20:03:43 hostname kscreen_backend_launcher[521]: kscreen.xcb.helper: Event Error: 147
Feb 04 20:03:45 hostname kscreen_backend_launcher[560]: kscreen.xcb.helper: Event Error: 147
Feb 04 20:03:49 hostname kdeinit5[470]: Failed to open layout memory xml file for reading "/home/user/.local/share/kded5/keyboard/session/layout_memory.xml" error: 5

mauritiusdadd · 2015-02-05 07:37:52

Well, I see only some minor errors but nothing that should prevent plasma to load.
Can you switch in another TTY and check what program is actually running?

ps -Af | grep kwin
ps -Af | grep plasma
ps -Af | grep ksplash

If both plasmashell and kwin_x11 are running, try to kill ksplash

killall ksplashqml

and see if the desktop environment works as expected.

Last edited by mauritiusdadd (2015-02-05 07:38:17)

amartin · 2015-02-05 13:48:37

Good idea, however both kwin_x11 and plasmashell are running, but ksplash is not running. Note that logging into cinnamon as this user works normally (so it's definitely KDE-specific)

mauritiusdadd · 2015-02-05 15:23:43

As a last attempt, try to rename each of the following files, if present, for example by adding the suffix .old (they should be recreated after a reboot but if something goes wrong you can restore them):

~/.config/kded5rc
~/.config/kdeglobals
~/.config/kscreenlockerrc
~/.config/ksplashrc
~/.config/kwinrc
~/.config/plasma-org.kde.plasma.desktop-appletsrc
~/.config/plasmarc
~/.config/plasmashellrc
~/.config/startupconfigfiles
~/.config/startupconfigkeys
~/.config/systemsettingsrc

I'm sorry but if even this does not work then probably the simplest solution is to back-up your data and create a new user with the same name.

amartin · 2015-02-05 15:41:34

Can I just move ~/.config to ~/.config.old to test recreating all of these files?

mauritiusdadd · 2015-02-05 16:16:44

Yes, you can: probably it is the fastest way to check if the problem is in there but note that by doing this you will lose/reset the configuration for a lot other of programs.

mrunion · 2015-02-05 19:55:36

Personally, I think it would be faster to create a new user and log in as the new user. That should definitely rule out any user config settings causing the problem.

amartin · 2015-02-06 02:37:43

I tried to move ~/.config to ~/.config.old but not improvement in behavior. I have now transitioned to a new profile - thanks for the help!

Arch Linux

#1 2015-02-04 04:17:03

[SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#2 2015-02-04 07:48:40

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#3 2015-02-04 13:57:39

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#4 2015-02-04 14:04:17

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#5 2015-02-04 14:40:15

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#6 2015-02-04 15:14:55

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#7 2015-02-05 03:03:04

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#8 2015-02-05 07:37:52

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#9 2015-02-05 13:48:37

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#10 2015-02-05 15:23:43

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#11 2015-02-05 15:41:34

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#12 2015-02-05 16:16:44

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#13 2015-02-05 19:55:36

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

#14 2015-02-06 02:37:43

Re: [SOLVED] Logging in from SDDM to Plasma 5 results in loading bar

Board footer