| Summary: | crash on launch: [Project::projectFileManager -> extension<KDevelop::IProjectFileManager>] | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Bruno Friedmann <bruno> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bubu.fearn, christian.gonzalez, markuspg |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | crash konsole log | ||
|
Description
Bruno Friedmann
2014-02-17 08:36:50 UTC
*** Bug 334950 has been marked as a duplicate of this bug. *** *** Bug 341422 has been marked as a duplicate of this bug. *** Created attachment 89777 [details]
crash konsole log
Here is a crash console log. I cant reproduce it EVERY time,mut sometimes it crashes directly after start, dometimes after pressing "execute", sometimes after "execute -> OK" using a new python project. Better ("crashier") results after rm'ing ~/./kde/share/config/kdeveloprc and ~/.kde/share/apps/kdevelop
This is odd indeed. Can you try the valgrind command I mentioned in the other bug report? Maybe we find out whats going on then. Otherwise, could you try to install cmake and git, and see if that has any effect? (Not that it should, just want to see what is going on here). Already running... (BTW, I found out it's --track-originS, not -origin...) - but I don't really have ever worked with valgrind. I just typed in the command, omitted the "-s" session option and am awaiting the output, to just post it here. There are miexd outputs from valgrind and kdevelop, does that matter?, can I redirect the valgrind output only in a file? Right, sorry for the typo. And the mixed output shouldn't matter, it's easy enough to only find the interesting bits and pieces from valgrind. thanks! keep us posted To be honest, I lost patience. After kdevelop crashing all the time without getting further, then crashing drkonqui (!) and then crashing plasma (again) - I lost my head. Bye to KDe this time again. Sorry that I can't help further here. *** Bug 348246 has been marked as a duplicate of this bug. *** 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! |