Summary: | Mount point editing doesn't change fstab | ||
---|---|---|---|
Product: | [Applications] partitionmanager | Reporter: | Alexey <esbodev> |
Component: | general | Assignee: | Andrius Štikonas <andrius> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugseforuns, nosewings |
Priority: | NOR | ||
Version: | 4.0.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/system/kpmcore/commit/5b80c6045c5306e5e61f963d30c0a9b8773e5407 | Version Fixed In: | 4.2.0 |
Sentry Crash Report: |
Description
Alexey
2020-02-05 19:34:37 UTC
*** This bug has been marked as a duplicate of bug 411841 *** Git commit 5b80c6045c5306e5e61f963d30c0a9b8773e5407 by Andrius Štikonas. Committed on 10/09/2020 at 22:54. Pushed by stikonas into branch 'fstab'. Fix fstab editing functionality. In the old code QByteArray fstabContents was actually empty. Also, writeData function was opening file in append mode, thus nothing was actually written. Split writeData function into two: * one for block devices * another for writing fstab file M +2 -2 src/core/fstab.cpp M +40 -1 src/util/externalcommand.cpp M +1 -0 src/util/externalcommand.h M +35 -3 src/util/externalcommandhelper.cpp M +2 -0 src/util/externalcommandhelper.h https://invent.kde.org/system/kpmcore/commit/5b80c6045c5306e5e61f963d30c0a9b8773e5407 *** Bug 411841 has been marked as a duplicate of this bug. *** *** Bug 427623 has been marked as a duplicate of this bug. *** |