Bug 187988 - plasma doesn't start after log in
Summary: plasma doesn't start after log in
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-24 10:56 UTC by Vladimir Eremeev
Modified: 2018-09-04 19:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Eremeev 2009-03-24 10:56:13 UTC
Version:            (using KDE 4.2.1)
Compiler:          gcc (Ubuntu 4.3.2-1ubuntu12) 4.3.2  
OS:                Linux
Installed from:    Ubuntu Packages

After entering login name and password I see the appearing icons, showing the load process, and I hear the startup sound. 

Then I see the black screen and the mouse cursor, and nothing else.

~/.xsession-errors contains nothing about plasma: search though the file for 'plasma' shows 'string noyt found'.

If I press Alt-F2 and enter 'plasma', then it starts.
Comment 1 Aaron J. Seigo 2009-03-25 01:27:11 UTC
plasma is started using an autostart .desktop file. please ensure this is properly installed. ask in the kubuntu help forums if you need user support in doing this.
Comment 2 Vladimir Eremeev 2009-03-25 12:44:34 UTC
Yes, the plasma.desktop was missing.
Comment 3 Vladimir Eremeev 2009-03-26 09:28:55 UTC
However, this means that the package kdebase-workspace-data 4:4.2.1a-0ubuntu1~intrepid3 is missing some necessary files.
I've taken the missing file from the respective package for KDE 4.1.4.
Comment 4 Andrew Crouthamel 2018-09-04 19:16:01 UTC
Hello! Plasma 4 was replaced by Plasma 5 four years ago by the KDE community. In that time we have made great strides in stability and functionality. We are closing all Plasma 4 bugs as most of them are no longer applicable to the new frameworks Plasma 5 is built upon. If you could, please re-test with the latest version of Plasma 5, and submit a new bug to "plasmashell" if you continue to have an issue. Thank you!