Bug 461848
Summary: | KDE 4.1 won't start (Plasma segfault) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Victor Lorenz <victor.lz> |
Component: | kdebase-workspace | Assignee: | Than Ngo <than> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | bughunt, fedora, kevin, ljhouwang, ltinkl, rdieter, tuxbrewr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-09-13 22:13:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Victor Lorenz
2008-09-10 21:56:07 UTC
That's strange because it works for me and many others on F9 x86_64. Googled the issue amd found that identical problem happened with Kubuntu e.g. http://kubuntuforums.net/forums/index.php?topic=3096602.0 Perhaps, unwisely, I tried what I thought might be same solution i.e delete./kde (maybe should have deleted .kde/share/kde4). KDE 4.1 now opens but obviously did some, but surprising little, damage, mainly to kmail. Can copy some stuff from .kde.BAK but obviously this is not optimal solution to problem. I had exactly the same problem after the update of Sept. 10. Please report crashes,segfaults upstream to bugs.kde.org. They're the ones best equipped to address such issues. (When/if you do, please let us know) Issue has already been reported to bugs.kde.org: KDE bug 170856 thx! Thanks for reporting upstream.. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. *** Bug 462448 has been marked as a duplicate of this bug. *** |