| Summary: | KDE partition manager crashes when try to access a NTFS partition | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | stapia <stapiax> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | alois1, linux |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
stapia
2019-06-29 17:01:26 UTC
Hm, I guess that partitionmanager somehow thinks the partition has size zero (i.e. it is corrupted. What does lsblk show for the size of the partition? 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! (In reply to Bug Janitor Service from comment #3) > 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! This bug is fixed in master. I have already provided information with the "crash report" before. Generally I could figure out, if you put several task in the task queue of the KDE Partition Manager and go for execution than very often a problem occurs. E.g. something like these together deleting, resizing, reformating et cetera. No problems seem, if you only do one task including execution but not more. (In reply to Andrius Štikonas from comment #4) > (In reply to Bug Janitor Service from comment #3) > > 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! > > This bug is fixed in master. Why did you repoen the bug? Have you tried master and it still crashed? (In reply to Andrius Štikonas from comment #6) > Why did you repoen the bug? Have you tried master and it still crashed? You wrote before: > due to lack of needed information. This is why I have given further information and reopened the issue. Happily if this bug would be fixed, because it causes fundamental problems for the users, isn't it. But I keep it closed, if it is already in the process of fixing. Not so easy to understand your status logic. > Not so easy to understand your status logic.
In the KDE bug tracker, a ticket is marked as RESOLVED when there is no more work to be done for this specific issue. Getting the fix to the users involves many more steps (e.g. branching, releasing tarballs, packaging by the distributions, etc.) but all of these are not tied to a specific ticket.
*** This bug has been marked as a duplicate of bug 413418 *** |