| Summary: | Does not exits on Ctrl-Q or from file menu or window close icon, blocks system shutdown | ||
|---|---|---|---|
| Product: | [Applications] krusader | Reporter: | bugs.kde.org |
| Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | krusader-bugs-null, nikita+kde |
| Priority: | NOR | Keywords: | triaged |
| Version First Reported In: | 2.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Debian based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
bugs.kde.org
2018-03-27 15:41:47 UTC
Do you use network fs actively? Which protocols? Is there any list of steps that reproduces the problem 100% times? Can you try git version and use -d flag, and then attach output here? Do you use network fs actively? Yes I do, but rarely. It seems that it's not connected to that. Not 100% sure, I'll watch out if I have tabs with network shares open. Which protocols? SMB mostly. I have few SFTP connections but they are used even less. Is there any list of steps that reproduces the problem 100% times? I haven't found that there is. I was looking to reproduce this but with no effect. Can you try git version and use -d flag, and then attach output here? Not sure that I can. Is there a way to get logs out of released version? Or any other way to see what's bloking the Quit dialog? Thanks for the update; changing status. > Not sure that I can. Is there a way to get logs out of released version? No problem. Current version doesn't have the functionality. We'll be releasing a new stable version in about 2 weeks, which will contain the flag and maybe even fixes your issue. We won't know until you check on your end. > Or any other way to see what's bloking the Quit dialog? Unfortunately, this is likely not solvable until we get a clue about the reasons. Let's see what new version does and go from there. Please try v2.7.0 that's been released recently and try running it with `-d` if the problem still exists. 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! |