| Summary: | Plasma keeps crashing, file:// protocol disappear? | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Nicolas Bigaouette <nbigaouette> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | Ivlev.Aleksej |
| Priority: | NOR | ||
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Nicolas Bigaouette
2012-01-16 16:44:02 UTC
I might have found the issue: a bad package was changing owners in /var/tmp and /tmp. I have not experienced the issue since a couple of hours. I will report back if I'm hit with the crash again. This open another question though. Instead of crashing, KDE should report what is wrong. I remember having been hit by another problem: I couldn't logging at all. KDE was reporting cryptic error and sending me back to KDM. The problem was that /tmp was full. It would be nice if KDE could detect these kind of problems and report to the user: clean up /tmp, wrong permissions, etc. Thanks Created attachment 83136 [details]
New crash information added by DrKonqi
plasma-desktop (4.11.2) on KDE Platform 4.11.2 using Qt 4.8.4
When my Kubuntu hust started, Dolphin (file browser) works fine, but suddenly it says, that it's wrong protocol "file".
-- Backtrace (Reduced):
#7 QDataStream::operator>> (this=this@entry=0x0, i=@0xbfb0c00c: -1254483273) at io/qdatastream.cpp:722
#8 0xb63b06a1 in KServiceGroupFactory::KServiceGroupFactory (this=0xc282b98) at ../../kdecore/services/kservicegroupfactory.cpp:43
#9 0xb63b093c in self (this=0x989f368) at ../../kdecore/sycoca/ksycocafactory.h:200
#10 KServiceGroupFactory::self () at ../../kdecore/services/kservicegroupfactory.cpp:62
#11 0xb63ab2bc in KServiceGroup::root () at ../../kdecore/services/kservicegroup.cpp:714
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! |