| Summary: | kdevelop crash upon closing | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Bucky <bucky> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | |
| Priority: | NOR | Keywords: | drkonqi, triaged |
| Version First Reported In: | 5.0.2 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Bucky
2016-11-16 21:26:16 UTC
Would "clearing out your home directory" include removing ~/.cache? If yes, did you close kdevelop before doing that? Actually, it involved dropping to single user mode, creating a new user with useradd, renaming my home directory to "oldme", renaming the new user directory to what my own home directory should be, chown-ing it to myself, then removing the new user and rebooting. There's probably a better way. But this gave me a completely fresh home folder, but not SO fresh that it didn't have the normal skeleton, and I could copy stuff I could actually identify as "I know what this is" back over. So yes, all that stuff was gone. Upon re-launch, kdevelop said, "Hey, you crashed. Do you want me to ignore the cache?" I said yes. It's been fine since then. Is that the issue? The project file pointing at a non-existent .cache folder? That doesn't seem right, if your .cache is empty, from my knowledge you shouldn't get the "it crashed" dialog -- the flag for that is stored in the cache. The project file contains no reference to the cache folder. Are you sure you didn't copy over (part of) .cache in the process, maybe even with issues like wrong permissions on the files? Oh. For clarity. The sequence of events after the new home directory was: Reboot. Rebuild my menu "favorites." Launch kdevelop. Choose a project. Kdevelop goes weird. Boom. Also plasmashell deadlocks. control-alt-f2 kill -HUP X11 Login again Relaunch kdevelop. Everything seems normal again (except the plasmashell deadlocks continue, but that's a different bug). It's the re-launch where kdevelop detected the crash, and after which everything was okay. Ah ok, that makes more sense. Thanks for the clarification. Maybe there's an issue when you close a project which is currently being opened or so. Maybe you can reproduce it? Hmm. If that' it, it's hard to trigger. One interesting thing. I always use "Pick Session." If you open a project, and close the window immediately, the project vanishes from my "Pick Session" list. The initial condition--the one where the project directory and its children appeared, but the child folders didn't have any expando arrows, and kdevelop crashed when I closed it (and then invited me to report it)--doesn't seem to be easy to trigger, either. I tried quitting, deleting the .cache folder, and re-launching, but kdevelop remained happy as a clam. Ordinarily a good thing. Not when attempting to create a recipe for reproducing an error, though. Since plasmashell was locking up at the same time, I'm willing to consider this a secondary crash caused by the first. I see xcb_conn_wait in the backtrace (I know it's involved in the plasmashell problem somehow, but I'm bad at reading backtraces). May we close this, and then if it ever happens to me again, I'll reopen--hopefully with a more well-defined way to reproduce? 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 set the bug status 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! Dear Bug Submitter, 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! |