Bug 321723 - Black screen at start up when selecting "Start with empty session" and choosing menubar style: "Title bar button"
Summary: Black screen at start up when selecting "Start with empty session" and choosi...
Status: RESOLVED WORKSFORME
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: 4.10.80
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-28 17:09 UTC by Esokrarkose
Modified: 2023-02-11 03:52 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 Esokrarkose 2013-06-28 17:09:45 UTC
When I select "Start with empty session" using latest master builds and kde 4.11 beta 1 I get an black screen only showing a mouse cursor for half of a minute (my pc is very modern and fast, just to note that). The fan is going up until plasma shows up, then everything is normal and you can start working. The start up process takes ages and is very unpredictable right now using that setting, which is a major bug in usability. 

Reproducible: Always

Steps to Reproduce:
1. Go to Systemsettings / System Administration / Startup and Shutdown / Session Management tab
2. Under "On Login" Section choose "Start with empty session"
3. Log out and log in again and you will see a black screen lasting for a longer time before finally showing plasma workspace 


Expected Results:  
After Splash screen ends Plasma workspace (Panels, Wallpaper etc.) should be instantly visible as it used to be.
Comment 1 Esokrarkose 2013-06-28 17:48:55 UTC
Found out that the long black screen is also related to another setting (combined with Start with empty session, as it does not happen with restore last session) :
You have to choose  Menubarstyle: Title bar button under: Systemsettings / Commom Appearance and Behavior /  Application Appearance / Style / Fine tuning tab /
This settings combined are responsible for the problem.
Comment 2 Esokrarkose 2013-06-28 18:13:56 UTC
The issue is more complex than initially thought: It is related to more than two settings. When I have more time I will add more information here. 
Here is my .kde directory which makes the problem 100% reproducable:
(only a few settings changed on a new install). I will give a list of what exactly I have changed when I have time as I remember everything and I will play with the settings a bit. 

http://ubuntuone.com/5LwzClGBAD2IUzMyTIGukj
Comment 3 Esokrarkose 2013-06-28 18:24:33 UTC
Okay, I have tried it again by deleting my .kde directory. Everything was fine then. Then I made the following changes:
Menubarstyle: Menubar button
Start with empty session
and moved all window buttons to the left. I made no additional changes elsewhere (not in plasma not in dolphin not in any other program.) That is 100% everything I did. 
Then I logged out and by logging in the next time the problem appeared. 
Here the new .kde folder:
http://ubuntuone.com/1rdMH5MfwtFbQFeaKm9qFp
Comment 4 Esokrarkose 2013-06-28 18:28:20 UTC
Okay I have given up on this issue ... odd enough the second kde folder linked here does work fine (sth. seemed to have changed before uploading). This issue is to complex for me. I hope the devs can get enough info from the first .kde folder.
Comment 5 Esokrarkose 2013-06-29 08:29:38 UTC
Just one note: The first .kde directory was made after deleting a previous .kde directory. No upgrades were made inbetween, so there is no orphaned config. I hope someone takes a look at it, because it seems a few config changes can make the system start very slowly. The bad thing I noticed is, that this seems to be very randomly, so if you use the first directory and logout and in a few times startup times will get normal again, but if you change some config again it can last very long.  

The certain component of this bug is, that splash seems to end much too soon, so that you are left with a black screen and can watch plasma loading, which should not be the case.
Comment 6 Andrew Crouthamel 2018-11-10 03:23:19 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-11-21 04:40:59 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Justin Zobel 2023-01-12 01:58:07 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 9 Bug Janitor Service 2023-01-27 05:07:31 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-02-11 03:52:15 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!