| Summary: | Crash at startup of plasma | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | BRULE Herman <alpha_one_x86> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | marco |
| Priority: | NOR | ||
| Version First Reported In: | 1.0.80 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
BRULE Herman
2011-03-06 12:34:39 UTC
Hi all, I recently switched to KDE on fedora 15 after gnome 3 came on (but also used KDE some years ago). I noticed that plasma crashed sometimes when configuring the desktop,plasmoids etc. and it crashed always at startup. Problem I saw was that some of the desktop settings were lost after a plasma crash and some previous configurations came up. At startup,just before the crash I noticed old desktops were very shortly shown and it switched to some other settings. Trying to understand it I tried to minimize the startup programs. Unusual thing was that plasma-desktop was listed twice. Removing one of them in turn in the System Settings caused KDE to start without displaymanager or menu. Still one plasma-desktop was in the startup scripts. Finding at autostart scripts I found a mess, scripts in: ./.config/autostart ./.kde4/Autostart ./.kde/Autostart ./.kde/share/autostart I brutally moved .kde to .kde-old because I'm running KDE4 after all. Now KDE started much cleaner. I saw the KDE init screen (with the five icons popping up) which was not the case before. Plasma didn't crash any more but desktop was empty. Added the systembar manually and was able to work normally. Okay, I lost some application settings from the .kde folder but a new .kde folder was created automatically and it was easy to copy some of the settings back. So I hope this helps to find the real bugs... 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! 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! 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! |