Bug 404664 - Can't login into Wayland session with current user but can do it with fresh
Summary: Can't login into Wayland session with current user but can do it with fresh
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.15.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-21 21:26 UTC by sunwebrw
Modified: 2019-02-22 19:12 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sunwebrw 2019-02-21 21:26:31 UTC
SUMMARY
Basically as the title says. I can't login into Wayland session, the screen goes black and nothing is happening.
But i can enter Wayland with newly created user.
My first thought was to bisect it by simply removing .local .config .cache see if it works and go from there but it didn't help at all. Then i took new users bashrc xinitrc and so on. When that didn't workout i simply copied everything(.local,.config,.bashrc,.xinitrc etc.) but baloo index files to this new user, changed ownership, and... he still could log in wayland session. Why?

It seems sddm wayland logging just don't work or doesn't catch it. 

Where else user specific data might be stored?

I could ofcourse create the new user and simply transfer all of my settings there but if this thing will keep on happening from time to time it won't be fun.
Comment 1 sunwebrw 2019-02-22 04:47:31 UTC
Ok, i've found the problem. I've had ssh-add command running on system startup and it was causing plasmashell to not load. I leave this open for now until i test this with some other DE. However it is still strange, how can a console utility cause this?
Comment 2 sunwebrw 2019-02-22 19:12:08 UTC
Ok, it happens in gnome-shell as well. Who'd knew that console utility could crash graphical session :\
Not a KDE bug.