[digikam] [Bug 374450] DATA LOSS: Saving a file can overwrite other file
https://bugs.kde.org/show_bug.cgi?id=374450 --- Comment #2 from Simon Persson --- I have now upgraded my installation to version 5.4.0 and the behaviour has not changed, still a problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374450] New: DATA LOSS: Saving a file can overwrite other file
https://bugs.kde.org/show_bug.cgi?id=374450 Bug ID: 374450 Summary: DATA LOSS: Saving a file can overwrite other file Product: digikam Version: 5.3.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: showfoto Assignee: digikam-de...@kde.org Reporter: simon.pers...@mykolab.com Target Milestone: --- Steps to reproduce: 1. Open folder with photos using the "open folder" button. 2. Select a photo to edit by double-clicking on it in the thumbbar. 3. Make some edit to the photo. 4. Select another photo in the thumbbar, single click only. 5. Click "Save". The problem is that the modified photo is now written to the filename of the current selection in the thumbbar, overwriting the contents of that file. I assume this is not the intended function, at least I found it very unexpected. This happened to me several times, each time I noticed the data loss I restored the overwritten photo from backup and continued editing other photos. Then it happened again, and again. Took me a long time to understand what was going on. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 465491] Interval schedules: save backup asap after missed schedule time
https://bugs.kde.org/show_bug.cgi?id=465491 Simon Persson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Summary|Kup on daily interval |Interval schedules: save |schedule - no backup after |backup asap after missed |suspend |schedule time --- Comment #4 from Simon Persson --- OK, excellent. Then it actually behaves as designed then. I agree that saving a new backup as soon as possible after a missed schedule would be good to have, and users would be right to expect it. For anyone who has time and interest to help fix this problem: The current scheduler goes to sleep with a duration which is the remaining time until next "backup save time". The solution here could be to instead just sleep 5 minutes and then upon wake up, check if it's time to save a new backup. If not, go back to sleep for another five minutes. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Backup folder not created for external disk plans
https://bugs.kde.org/show_bug.cgi?id=453919 --- Comment #9 from Simon Persson --- Git commit e78e02a49bce15fa8cc81070da0ba1b42e01d119 by Simon Persson. Committed on 22/02/2023 at 22:02. Pushed by persson into branch 'master'. Create multiple levels of directories for backup destination For external disk executor, user can specify a path to use on the destination storage volume. This change makes destination directory creation work also for paths more than 1 level deep. M +1-1daemon/edexecutor.cpp https://invent.kde.org/system/kup/commit/e78e02a49bce15fa8cc81070da0ba1b42e01d119 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 465491] Interval schedules: save backup asap after missed schedule time
https://bugs.kde.org/show_bug.cgi?id=465491 Simon Persson changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/kup/commit/e09c9b1e9fcdc ||34d157c383694dee5e00cf091e3 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Simon Persson --- Git commit e09c9b1e9fcdc34d157c383694dee5e00cf091e3 by Simon Persson. Committed on 22/02/2023 at 21:25. Pushed by persson into branch 'master'. Change sleep duration for interval plan executor The problem was that time spent with computer in suspend mode was not advancing the process timer. So backup saving every 24 h would happen 27 hours after last save if three hours was spent suspended. Fix by checking if it's time to save every five minutes. M +4-2daemon/planexecutor.cpp https://invent.kde.org/system/kup/commit/e09c9b1e9fcdc34d157c383694dee5e00cf091e3 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Backup folder not created for external disk plans
https://bugs.kde.org/show_bug.cgi?id=453919 Simon Persson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #10 from Simon Persson --- I have tried reproducing this bug but failed, the destination folder always gets created for me. Except if you set a destination path like "Backu/ps" (more than one directory that needs to be created). That has now been fixed. For any of the people reporting this bug, please try to provide more details. I don't really know what details to be honest, I have no good idea what could be happening. All reporters say that you needed to create the folder yourself and then saving backups started working (except some user that also needed to run bup init). Has anybody tried deleting the folder after a backup was saved there? Does kup go back to not doing anything again? (It should still work, and does still work when I tested) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448901] Backup list item has white font on light blue background which is hardly readable
https://bugs.kde.org/show_bug.cgi?id=448901 Simon Persson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/commit/95922f5f1a45a ||0694ac1ad285d7c1dedd5d5a54e Resolution|--- |FIXED --- Comment #2 from Simon Persson --- Git commit 95922f5f1a45a0694ac1ad285d7c1dedd5d5a54e by Simon Persson. Committed on 22/02/2023 at 22:59. Pushed by persson into branch 'master'. Fix text color in DriveSelectionDelegate M +1-2kcm/driveselectiondelegate.cpp https://invent.kde.org/system/kup/commit/95922f5f1a45a0694ac1ad285d7c1dedd5d5a54e -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 463016] Kup: asking for confirmation even if option disabled
https://bugs.kde.org/show_bug.cgi?id=463016 Simon Persson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |INTENTIONAL --- Comment #1 from Simon Persson --- There is a check to see if computer is in power save mode and if it is then Kup will always ask if you wish to save a backup. Could that be what you are seeing? -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 460209] Run command before & after backup
https://bugs.kde.org/show_bug.cgi?id=460209 Simon Persson changed: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Simon Persson --- Thanks for reporting your idea and motivation! This is an idea that could be accepted, if somebody wants to work on it. Mostly about getting a nice configuration UI. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 454773] Way to run plan from command line/cron etc.
https://bugs.kde.org/show_bug.cgi?id=454773 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/commit/f4243be1af1dd ||3126f10767f4966e5936a55a2d9 --- Comment #1 from Simon Persson --- Git commit f4243be1af1dd3126f10767f4966e5936a55a2d9 by Simon Persson. Committed on 23/02/2023 at 21:55. Pushed by persson into branch 'master'. Add a public method saveNewBackup M +7-0daemon/kupdaemon.cpp M +1-0daemon/kupdaemon.h https://invent.kde.org/system/kup/commit/f4243be1af1dd3126f10767f4966e5936a55a2d9 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 458327] No indication that destination must exist for backup to proceed
https://bugs.kde.org/show_bug.cgi?id=458327 Simon Persson changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/kup/commit/13b10dad891d2 ||81e2a0c6aac7c15211bb8dbd692 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Simon Persson --- Git commit 13b10dad891d281e2a0c6aac7c15211bb8dbd692 by Simon Persson. Committed on 24/02/2023 at 00:28. Pushed by persson into branch 'master'. Add warnings to user about problems with filesystem destination Related: bug 445391 M +50 -1kcm/backupplanwidget.cpp M +3-0kcm/backupplanwidget.h https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 445391] Selecting a SMB network share results in "backup destination cannot be reached"
https://bugs.kde.org/show_bug.cgi?id=445391 Simon Persson changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/kup/commit/13b10dad891d2 ||81e2a0c6aac7c15211bb8dbd692 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Simon Persson --- Git commit 13b10dad891d281e2a0c6aac7c15211bb8dbd692 by Simon Persson. Committed on 24/02/2023 at 00:28. Pushed by persson into branch 'master'. Add warnings to user about problems with filesystem destination Related: bug 458327 M +50 -1kcm/backupplanwidget.cpp M +3-0kcm/backupplanwidget.h https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Backup folder not created for external disk plans
https://bugs.kde.org/show_bug.cgi?id=453919 Simon Persson changed: What|Removed |Added Resolution|WORKSFORME |FIXED Status|NEEDSINFO |RESOLVED --- Comment #13 from Simon Persson --- (In reply to Christian Hartmann from comment #12) > (In reply to Simon Persson from comment #10) > > Has anybody tried deleting the folder after a backup was saved there? > > Does kup go back to not doing anything again? (It should still work, and > > does still work when I tested) > > i tried this... > > 1. i moved (actualy just renamed) the used beforehand directory (on my > external disk). > 2. checked kup config via system settings - all unchanged > 3. tried to create backup via system tray symbol (with a so configured but > currently no existing directory) > 4. nothing happened / quite exit > > 5. renamed the renamed folder to its original name > 6. tried to create backup via system tray symbol (with the so configured and > now existing again directory) > 7. backup is created ... > > if it is helpful i can supply screenshots all of that Thank you, Christian, for trying! I see now that I actually made a fix for this problem almost two years ago and had completely forgotten about that. So I was of course testing with the latest version and could not see any problem. So sorry for my confusion here! At least, good thing that I have an explanation. So Already fixed, will be solved for users once I find the time to make a new release. Thanks again to all who reported and commented! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 463000] Removing a backup plan removes names from subsequent plans
https://bugs.kde.org/show_bug.cgi?id=463000 Simon Persson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Simon Persson --- *** This bug has been marked as a duplicate of bug 451679 *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 451679] backups configuration inconsistency after removing one plan
https://bugs.kde.org/show_bug.cgi?id=451679 Simon Persson changed: What|Removed |Added CC||pub...@mellomrommet.no --- Comment #1 from Simon Persson --- *** Bug 463000 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 451679] backups configuration inconsistency after removing one plan
https://bugs.kde.org/show_bug.cgi?id=451679 Simon Persson changed: What|Removed |Added CC||qsabip...@mozmail.com --- Comment #2 from Simon Persson --- *** Bug 460998 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460998] Backups reset when I delete one of them
https://bugs.kde.org/show_bug.cgi?id=460998 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Simon Persson --- *** This bug has been marked as a duplicate of bug 451679 *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482497] rsync backup plan fills up backup disk when it shouldn't
https://bugs.kde.org/show_bug.cgi?id=482497 Simon Persson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #3 from Simon Persson --- Do you want these folders to be included? > /home/nate/kde/build/kitemmodels > /home/nate/kde/build/knotifyconfig > /home/nate/kde/usr/bin In other words, are you reporting a problem with the folder selection being used not matching with what you have selected? Do these folders contain enough large files to explain the problem of running out of space? Is there any problem with folders that should be excluded still getting copied? Kup is already doing the safest but possibly slower option of deleting everything that should be deleted before copying anything. Meaning that if it can fit on the destination it will work. This --delete-before option implies --no-i-r so that is no actual difference. I would understand if your version caused problems with running out of space but you are reporting the opposite. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 481540] Can't use filesystem directory as destination
https://bugs.kde.org/show_bug.cgi?id=481540 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/kup/-/commit/769ef9be926 ||3a5856da0974ca133d1571d480e ||2b --- Comment #1 from Simon Persson --- Git commit 769ef9be9263a5856da0974ca133d1571d480e2b by Simon Persson. Committed on 13/03/2024 at 20:17. Pushed by persson into branch 'master'. Port away from QSignalMapper::mapped signals These overloaded signals were removed in Qt6. Qt5.15 contains the replacement signals, same as qt6. M +3-3kcm/kbuttongroup.cpp https://invent.kde.org/system/kup/-/commit/769ef9be9263a5856da0974ca133d1571d480e2b -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 481468] "Filedigger" and "Purger" are not opening
https://bugs.kde.org/show_bug.cgi?id=481468 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Simon Persson --- This was fixed back in 2021, just haven't had time/energy/motivation to make a release. Sorry. Thanks for reporting! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482015] Kup system tray icon and settings module missing on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482015 Simon Persson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/kup/-/commit/9dc491cc785 ||2112c3745056759c53a83574cc4 ||ab --- Comment #11 from Simon Persson --- Git commit 9dc491cc7852112c3745056759c53a83574cc4ab by Simon Persson. Committed on 17/03/2024 at 18:42. Pushed by persson into branch 'master'. Add a version of the plasmoid that works on plasma 6 This commit does the following: - Move existing plasmoid to plasmoid-qt6 and finish qt6 port. - Add plasmoid-qt5 folder with contents of commit eae3138eaa, before q6 port was started. - Change CmakeLists.txt to install one of the two versions. M +2-1CMakeLists.txt C +8-9plasmoid-qt5/contents/ui/FullRepresentation.qml [from: plasmoid/contents/ui/FullRepresentation.qml - 089% similarity] C +19 -28 plasmoid-qt5/contents/ui/main.qml [from: plasmoid/contents/ui/main.qml - 058% similarity] C +0-0plasmoid-qt5/metadata.json [from: plasmoid/metadata.json - 100% similarity] R +24 -16 plasmoid-qt6/contents/ui/FullRepresentation.qml [from: plasmoid/contents/ui/FullRepresentation.qml - 077% similarity] R +6-25 plasmoid-qt6/contents/ui/main.qml [from: plasmoid/contents/ui/main.qml - 068% similarity] R +1-1plasmoid-qt6/metadata.json [from: plasmoid/metadata.json - 099% similarity] https://invent.kde.org/system/kup/-/commit/9dc491cc7852112c3745056759c53a83574cc4ab -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 483222] Strange KCM message when there's a symlink pointing to a file that's not in the backup plan
https://bugs.kde.org/show_bug.cgi?id=483222 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/-/commit/f705664ce43 ||7ca2a40b4a91dadc4c3fe1e700d ||fd --- Comment #2 from Simon Persson --- Git commit f705664ce437ca2a40b4a91dadc4c3fe1e700dfd by Simon Persson. Committed on 17/03/2024 at 18:57. Pushed by persson into branch 'master'. Simplify warning text in KCM There is no need to say that the symlink is included, it's implied by the fact that a warning about it is displayed. M +4-4kcm/backupplanwidget.cpp https://invent.kde.org/system/kup/-/commit/f705664ce437ca2a40b4a91dadc4c3fe1e700dfd -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 481680] Restoring from Backup produces error
https://bugs.kde.org/show_bug.cgi?id=481680 Simon Persson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #9 from Simon Persson --- Thanks for the report! 1. Restoring /home instead of /home/user will normally fail with permission problem, as it has in your case. It's normal that only root has permission to write to that folder. 2. Crashing kioslave5 is interesting! I believe now, from the backtrace you saved here, that it has to do with reading file contents of some specific files. It would be helpful if you could narrow it down even more than what you have already done. I believe you will see the same crash by just using a "bup:///home/user/.local" URL in some KDE based file lister, like dolphin or gwenview. That could be a faster way to find an example (you had more than 1) file that causes the crash. It would also be interesting then if you could save a new backup (in a completely new backup destination folder) of a folder that has problematic files. Then see if there is the same problem with that backup. Fantastic reporting, thanks for taking the time! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 481680] Restoring from Backup produces error
https://bugs.kde.org/show_bug.cgi?id=481680 --- Comment #10 from Simon Persson --- Forgot to say, if you do narrow it down to a small backup that causes a crash when restoring... then if you are willing to share that with me it could be very helpful. Just zip up the backup destination folder and upload here or email me directly. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 431136] Request: Allow bup to make backups of root folders
https://bugs.kde.org/show_bug.cgi?id=431136 --- Comment #3 from Simon Persson --- Sorry for the late reply. Busy days. I decided quite early in the development of Kup that I didn't want to give people a false sense of security. So I never considered silently skipping files with problems. You could perhaps show a warning popup window or such. But I would still be hesitant to label that backup as successful (used for scheduling). -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426421] Kup won't finish backup - UnicodeDecodeError
https://bugs.kde.org/show_bug.cgi?id=426421 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Simon Persson --- *** This bug has been marked as a duplicate of bug 426139 *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426139] No Backup due to UnicodeDecodeError in error callback
https://bugs.kde.org/show_bug.cgi?id=426139 Simon Persson changed: What|Removed |Added CC||el...@seznam.cz --- Comment #3 from Simon Persson --- *** Bug 426421 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426139] No Backup due to UnicodeDecodeError in error callback
https://bugs.kde.org/show_bug.cgi?id=426139 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from Simon Persson --- Thanks for reporting! It seems many users are experiencing this after updating bup to version 0.31. Issue is reported and discussed here: https://groups.google.com/forum/#!topic/bup-list/Jaq_BACy7QU -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426139] No Backup due to UnicodeDecodeError in error callback
https://bugs.kde.org/show_bug.cgi?id=426139 --- Comment #9 from Simon Persson --- I think this has been fixed upstream. Found the following: https://groups.google.com/forum/#!topic/bup-list/Ifw6gZ6sxBA https://github.com/bup/bup/commit/eff166ca3ad17288b3114cc3c636c7b3d96ad155#diff-3f8c732e7bb07d7ef75a64f8effac28a So anyone who is eager enough to get this working can try latest bup from git. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426804] Filedigger launcher is confusing rsync users
https://bugs.kde.org/show_bug.cgi?id=426804 Simon Persson changed: What|Removed |Added Summary|cannot restore backup when |Filedigger launcher is |using rsync |confusing rsync users -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426804] Filedigger launcher is confusing rsync users
https://bugs.kde.org/show_bug.cgi?id=426804 Simon Persson changed: What|Removed |Added Priority|NOR |LO Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |minor --- Comment #1 from Simon Persson --- Filedigger was created to allow a merged view of backups, for each file or folder the user can see a list of timestamps and open or restore that specific one. For rsync type of backups that makes no sense since there only ever is one version saved. Also, since the users files are saved at the backup location just as a stright simple copy then it makes sense to just use a file browser to look at the saved files. User can copy anything they need from there. Keeping this bug report open since clearly there is improvement potential in how kup presents information, labeling of buttons etc. to make it clear what the user should expect from interacting with kup. Any suggestion for how to avoid misunderstandings is appreciated! Thank you for taking the time to report! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 427151] Versioned backup not available in kup-backup
https://bugs.kde.org/show_bug.cgi?id=427151 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Simon Persson --- Bup is coming back to debian. While waiting for that users can install bup version 0.31 directly from sources as a work around. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 422284] Recent distributions don't ship Bup anymore
https://bugs.kde.org/show_bug.cgi?id=422284 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Simon Persson --- Thomas, maintainer of kup debian package, contacted bup developers regarding this concern: https://groups.google.com/forum/#!topic/bup-list/bXhVRnt_cXE The way I see it it's not much to do but wait for this to get solved. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 422534] Wish: Support for remote Backups
https://bugs.kde.org/show_bug.cgi?id=422534 Simon Persson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Persson --- Hello and thanks for taking the time to write down your thoughts! When I first started Kup I had planned to add this, but then I never needed it myself and nobody asked for it. Not until now. So I don't think it's very common to do this, but of course it could become more common if support is added to Kup... Anyway, even if uncommon, it could be worth adding since I think it should be pretty easy. The tricky part is just figuring out scheduling logic with regards to knowing if the backup destination is available or not. I think doing a ping test every five or ten minutes should be good enough. Oh, and another tricky part is maybe storing password. I have not looked at how to do that. KWallet probably. If any volunteer wants to work on this, get in contact and we can figure out the details for how it should work. For myself, I might work on it if I get inspired one day but I'm not promising anything. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 428851] Kup crashes when opened
https://bugs.kde.org/show_bug.cgi?id=428851 --- Comment #2 from Simon Persson --- Thanks for reporting! I'm quite busy these days but will try to reproduce this crash when I have a chance. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 425693] KUP Backup cant be loaded
https://bugs.kde.org/show_bug.cgi?id=425693 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/commit/6b8e770584f6f ||6674f17a41b3424191e47e73dbc --- Comment #1 from Simon Persson --- Git commit 6b8e770584f6f6674f17a41b3424191e47e73dbc by Simon Persson. Committed on 23/08/2020 at 12:42. Pushed by persson into branch 'master'. Better handling of relative path argument to filedigger If you gave a relative path to bup repo as command line argument for kup-filedigger then it would work OK until you tried to open a file or folder with external program. Solve problem by making sure repo path is absolute, first thing. M +3-1filedigger/main.cpp https://invent.kde.org/system/kup/commit/6b8e770584f6f6674f17a41b3424191e47e73dbc -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 425693] KUP Backup cant be loaded
https://bugs.kde.org/show_bug.cgi?id=425693 --- Comment #2 from Simon Persson --- Thank you for reporting! Took a bit of trying to reproduce but I did figure out that giving a relative path as command line argument would cause what you reported. Easiest work-around for now would be for users to open kup-filedigger either from sys tray applet or from command line without any path argument (gives you a folder selector). -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 425693] KUP Backup cant be loaded
https://bugs.kde.org/show_bug.cgi?id=425693 --- Comment #4 from Simon Persson --- Ah, if you are using an older version then yes, a path argument is required. So, you can give an absolute path instead there. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402784] New: Dolphin crashes during shutdown, when stopping activity
https://bugs.kde.org/show_bug.cgi?id=402784 Bug ID: 402784 Summary: Dolphin crashes during shutdown, when stopping activity Product: dolphin Version: 18.12.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: simon.pers...@mykolab.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.12.0) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.8-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: How to reproduce: Press Win+Q, make sure that you have two plasma activities running. Start dolphin in current activity. Press Win+Q again and stop current activity. Dolphin crashes while it is stopping. It does not matter if you have another instance of dolphin running in the other activity. In the backtrace it looks suspicious that there is a recursive call to the destructor of KItemListViewAccessible. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f1495f800 (LWP 2117))] Thread 8 (Thread 0x7f1ef3fff700 (LWP 2133)): #0 0x7f1f1d3057a4 in read () from /usr/lib/libc.so.6 #1 0x7f1f18b70781 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1f18bc0a50 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f1f18bc1e86 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f1f18bc1fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f1f1b3f65c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1f1b39f58c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f1f1b1e35c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f1f1b1e49cc in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f1f19adea9d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f1f1d314b23 in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1f09a25700 (LWP 2128)): #0 0x7f1f19ae4afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f0b35fd94 in ?? () from /usr/lib/dri/swrast_dri.so #2 0x7f1f0b35fcd8 in ?? () from /usr/lib/dri/swrast_dri.so #3 0x7f1f19adea9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f1f1d314b23 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1f0a226700 (LWP 2127)): #0 0x7f1f19ae4afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f0b35fd94 in ?? () from /usr/lib/dri/swrast_dri.so #2 0x7f1f0b35fcd8 in ?? () from /usr/lib/dri/swrast_dri.so #3 0x7f1f19adea9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f1f1d314b23 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1f0aa27700 (LWP 2126)): #0 0x7f1f19ae4afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f0b35fd94 in ?? () from /usr/lib/dri/swrast_dri.so #2 0x7f1f0b35fcd8 in ?? () from /usr/lib/dri/swrast_dri.so #3 0x7f1f19adea9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f1f1d314b23 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1f0b228700 (LWP 2125)): #0 0x7f1f19ae4afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f1f0b35fd94 in ?? () from /usr/lib/dri/swrast_dri.so #2 0x7f1f0b35fcd8 in ?? () from /usr/lib/dri/swrast_dri.so #3 0x7f1f19adea9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f1f1d314b23 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1f11e90700 (LWP 2120)): #0 0x7f1f1d3057a4 in read () from /usr/lib/libc.so.6 #1 0x7f1f18b70781 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f1f18bc0a50 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f1f18bc1e86 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f1f18bc1fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f1f1b3f65c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f1f1b39f58c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f1f1b1e35c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f1f1b669ba6 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f1f1b1e49cc in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f1f19adea9d in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f1f1d314b23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1f1327a700 (LWP 2118)): #0 0x7f1f1d309c21 in poll () from /usr/lib/libc.so.6 #1 0x7f1f18676630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f1f186782db in xcb_wait_for_event () from /usr/
[kup] [Bug 472995] KUP cannot find firefox executable
https://bugs.kde.org/show_bug.cgi?id=472995 --- Comment #1 from Simon Persson --- The link is for a man:// URL, please check system settings for what will open on such a url. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 458327] No indication that destination must exist for backup to proceed
https://bugs.kde.org/show_bug.cgi?id=458327 Simon Persson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Simon Persson --- Thanks for reporting! It was indeed created with mounted folders in mind, so a destination folder not existing would be normal at most times. But like you say, the configuration module might be good time to insist that it should exist. It could offer to create the folder, maybe in a warning message. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 458326] Add manual trigger for backup
https://bugs.kde.org/show_bug.cgi?id=458326 Simon Persson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Simon Persson --- There is a button "save new backup" in the plasmoid, only visible when backup plan destination is available. Please confirm if you can see it. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 467477] kup-purger doesn't work
https://bugs.kde.org/show_bug.cgi?id=467477 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Simon Persson --- Thanks for reporting! I fixed this problem in commit 96c0bc820 back in july 2021 but I have not found the time and motivation to release a new version of kup since. I will try. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 463016] Kup: asking for confirmation even if option disabled
https://bugs.kde.org/show_bug.cgi?id=463016 Simon Persson changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 468269] Warn user if Destination Folder does not exist, or create it automatically
https://bugs.kde.org/show_bug.cgi?id=468269 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Simon Persson --- *** This bug has been marked as a duplicate of bug 453919 *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Backup folder not created for external disk plans
https://bugs.kde.org/show_bug.cgi?id=453919 Simon Persson changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #14 from Simon Persson --- *** Bug 468269 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 468269] Warn user if Destination Folder does not exist, or create it automatically
https://bugs.kde.org/show_bug.cgi?id=468269 --- Comment #2 from Simon Persson --- Thank you for reporting! It has been solved but the solution is not in a released version yet. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 451302] Kioslave crashes repeatedly in File::readMetadata() when trying to recover backup from /home or /home/user
https://bugs.kde.org/show_bug.cgi?id=451302 --- Comment #2 from Simon Persson --- Thanks for the bug report! I am unable to reproduce the problem. Looking at the code around the place of the crash I am also unable to imagine what could be going wrong there, my imagination is not good enough... :) To work towards a solution to this problem we will need to dig around a bit more in your saved backups, see what triggers this problem. I am thinking that this could be related to the stored content of a file, perhaps it has gotten corrupted somehow. This could be any file in your home folder, since when you select the top level directory Kup will be scanning absolutely every single file that was saved in there. So when you say that individual folders work fine, perhaps you were just lucky to try with folders that had no problem. If you want to help by looking for a file in your backups that triggers this problem, the easiest way is to just open dolphin and type in the address bar "bup:/path/to/backups". Then just navigate around there, into every saved directory. See if the bup kioslave crashes in the same way. I hope you managed to get your files restored! While you have this problem, the alternative way to restore files would be to just use "bup restore" directly. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 451679] backups configuration inconsistency after removing one plan
https://bugs.kde.org/show_bug.cgi?id=451679 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 426804] Filedigger launcher is confusing rsync users
https://bugs.kde.org/show_bug.cgi?id=426804 Simon Persson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #3 from Simon Persson --- Closing this bug. Nobody has suggested any better wording to avoid misunderstanding, I don't know how to make it clearer. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 444169] kup backup broken after pruning
https://bugs.kde.org/show_bug.cgi?id=444169 Simon Persson changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Simon Persson --- Thanks for the bug report! I am afraid this needs to be solved in bup. Please contact the bup mailing list to report the problem, I am sure this is valuable information because when I searched the mailing list archives, there had been several years of this pruning option being available but no reports of any problem with it. Another thing here, most likely unrelated... but I noticed from your log file that you have included for backup a folder located inside an excluded folder. This is still not supported by bup as far as I know, so check your backups to make sure all your files are actually being saved. (Kup still allows such a selection because rsync supports it). I have reported it to the bup developers together with a fix but they never did anything about it. Probably 7-9 years ago that I did that. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 450514] Clicking on "open log" in an error notification does nothing
https://bugs.kde.org/show_bug.cgi?id=450514 Simon Persson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Simon Persson --- This works for me. Can you confirm that the log file exists? Should be located at .cache/kup/kup_plan1.log inside your home folder. Also try opening it there, from your file manager. Let me know if that works for you. Possibly no application is configured to open .log files? -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 445391] Selecting a SMB network share results in "backup destination cannot be reached"
https://bugs.kde.org/show_bug.cgi?id=445391 --- Comment #7 from Simon Persson --- (In reply to Jacek Rzęsista from comment #6) > (In reply to Chris Rizzitello from comment #2) > > This is not a "bug" > > The end user must mount a SMB share to use as an rsync target. > > Rsync is known to not work well over the smb protocol > > > > The Issue at hand is that we need to communicate this to the user. If they > > select a location to store the backup that is a remote share it must be of > > sftp(ssh) or rsync type. If the user has selected a path mounted via kio > > like a temp smb path (i.e smb://server/share) in dolphin we need to warn > > that the path is temporary mount point. > > I have a question about sftp(ssh) type :) What kind of path do I have to set > in kup to get it work ? When I try path like this: > sftp://user@destination_ip/path_to_folder/on_destination > I still got tooltip in systray with info about that backup's destination is > unreacheable. What you can do is to install sshfs, mount the remote folder to some local folder, configure kup to save to some path under that local folder. Kup will monitor the local folder for mount and unmount events. So just make sure to always mount that server to the same local path. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 434986] option to configure kup with a right click on the tray icon
https://bugs.kde.org/show_bug.cgi?id=434986 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Persson --- Hello! Thanks for taking the time to suggest an idea. In fact this was recently added and will be part of the next released version. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 445391] Selecting a SMB network share results in "backup destination cannot be reached"
https://bugs.kde.org/show_bug.cgi?id=445391 Simon Persson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Simon Persson --- I agree that there could be an error message displayed to the user when selecting a path for local filesystem destination which is actually not in the local filesystem. I will work on adding that when I find the time, but if anybody wants to help... Please go ahead! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Buckups won't run, no errors given.
https://bugs.kde.org/show_bug.cgi?id=453919 --- Comment #1 from Simon Persson --- Is it possible that you had bup or rsync installed when you enabled backups? Then when making and running the backup plan you no longer have it on your computer? Just an idea to maybe explain what happened. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 431136] Request: Allow bup to make backups of root folders
https://bugs.kde.org/show_bug.cgi?id=431136 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Simon Persson --- I decided some time ago that system backup is not a goal for Kup, it's intended for personal files only. If you still want to use kup for this purpose then perhaps you can make the problematic files readable by a "backup" group and add your login user to this group. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 439852] Crashes when Background Opacity is enabled on QT-Curve
https://bugs.kde.org/show_bug.cgi?id=439852 Simon Persson changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Simon Persson --- Confirmed that I see the crash in the opening the kup settings module (run kcmshell5 kcm_kup). Did not try any other parts of kup. Tried looking at valgrind output and also a core dump with gdb. I have no idea what is going on there. If somebody feels like building all of kde and qt with debug symbols and get a useful backtrace, that could be a good start. I don't have time for that myself. Thanks for the report! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 483986] The Backup Status icon disappears from the System Tray after creating a new backup.
https://bugs.kde.org/show_bug.cgi?id=483986 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Simon Persson --- This was fixed in commit 270bdb6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448898] Add a way to trigger a backup right now
https://bugs.kde.org/show_bug.cgi?id=448898 Simon Persson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/-/commit/6c3e2c7e7d2 ||3fe3850a0fb7e90a7e03775394b ||16 Resolution|--- |FIXED --- Comment #2 from Simon Persson --- Git commit 6c3e2c7e7d23fe3850a0fb7e90a7e03775394b16 by Simon Persson. Committed on 01/05/2024 at 14:16. Pushed by persson into branch 'master'. Change wording for manual backup explanation M +2-2kcm/backupplanwidget.cpp https://invent.kde.org/system/kup/-/commit/6c3e2c7e7d23fe3850a0fb7e90a7e03775394b16 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 483209] Scheduled Backup fails to start on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483209 Simon Persson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Simon Persson --- What kup does is that when starting to save a backup it first checks if the storage volume is accessible, if not it will ask for the volume to be mounted and it goes back to passive state. If the volume never becomes accessible then kup will never continue with saving data. It sounds to me that perhaps something in the "solid" framework has stopped working in newer versions? That is the library that should ask for password and mount the storage volume. Simon Brown, can you try to enable automatic mounting for your storage device and see if this helps? -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482323] Save new backup button does nothing when backup fails to start
https://bugs.kde.org/show_bug.cgi?id=482323 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Simon Persson --- Destination folder creation has been fixed already, just not in a released software version yet. Thanks for reporting! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 467082] Kup/bup fails to save
https://bugs.kde.org/show_bug.cgi?id=467082 Simon Persson changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REOPENED|RESOLVED --- Comment #3 from Simon Persson --- Sorry that I have not followed up on this bug report for so long. Since this sounds very much internal to how bup saves data, the best hope of getting this fixed is to report to the mailing list for bup: https://groups.google.com/g/bup-list Thank you for reporting! And I'm sorry I can't help more than that. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 477002] Kup does not ask for confirmation consistently
https://bugs.kde.org/show_bug.cgi?id=477002 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Simon Persson --- Thanks for reporting! The intentional behavior is that you only get a question to confirm the first time after a backup destination becoming available. Any time after that will go ahead and save directly without asking. This is something that has been in Kup for a long time, I had forgotten about it. I would like your feedback on if you think this is a bad idea. I am not completely sure. I am also not sure if I remember the whole original motivation. It was about not disturbing the user too much, that if you said yes once then Kup should just assume that it is yes for the following times. If you say no (or ignore the question) then you will also not get asked again, even if yet another interval passes. You then need to start "manually" by clicking the button "Save new backup" and after that it will happen automatically without question. I will close this report as intentional but please share your thoughts! And please reopen if this is not does not explain what you see happening on your computer. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 469352] kup-purger from wayland session
https://bugs.kde.org/show_bug.cgi?id=469352 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Simon Persson --- Thanks for the report! I have now found the time to test this and I am not able to see any problem. Unfortunately it just works. I have tried version 0.9.1 (using latest versions of Qt5 and KF5 libraries). I have also tried latest, unreleased, version of kup. If you find that it still happens for you, please reopen this bug report and we will dig deeper. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 444704] 'Backup Status' widget displays an error message: 'Error, no connection to kup-daemon...'
https://bugs.kde.org/show_bug.cgi?id=444704 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/kup/-/commit/07ee384082f ||1b2efa7a57e120c0dd5dc17d435 ||aa --- Comment #5 from Simon Persson --- Git commit 07ee384082f1b2efa7a57e120c0dd5dc17d435aa by Simon Persson. Committed on 24/03/2024 at 21:09. Pushed by persson into branch 'master'. Remove connection error text from data source The error message displayed to user was not translated and regardless of what the problem was, would not help the user figure out how to solve it. If there even was a problem. Because it could also be displayed if the plasmoid was forced to be displayed even when kup backups was not enabled. M +1-5dataengine/kupengine.cpp https://invent.kde.org/system/kup/-/commit/07ee384082f1b2efa7a57e120c0dd5dc17d435aa -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 468242] [WISH] Add conditional start option for scheduled backups
https://bugs.kde.org/show_bug.cgi?id=468242 Simon Persson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Simon Persson --- Thanks for the report! This is already supposed to work, like Daniel M commented. When there is a change in file system mounts kup will check if the filesystem destination is available. This can fail to work if your local filesystem has the destination folder and it just gets shadowed (hidden) by mounting a networked filesystem, in that case the destination folder always exists. Please reopen this bug report if kup fails to notice changes in filesystem mounts or if I have misunderstood something. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 438078] Backup Plan 1 -- Purger
https://bugs.kde.org/show_bug.cgi?id=438078 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/kup/commit/c0503af8b057a ||a66b8ba76e26f4fc0f630774102 --- Comment #3 from Simon Persson --- Git commit c0503af8b057aa66b8ba76e26f4fc0f630774102 by Simon Persson. Committed on 05/06/2021 at 05:21. Pushed by persson into branch 'master'. Bugfix for unintentional start of kup-purger Had forgotten to initialize member variable to false. M +1-1daemon/edexecutor.cpp https://invent.kde.org/system/kup/commit/c0503af8b057aa66b8ba76e26f4fc0f630774102 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 437439] KDE-Neon: bup crashes
https://bugs.kde.org/show_bug.cgi?id=437439 Simon Persson changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Simon Persson --- Thanks for reporting! Looks like you don't have git installed. That should be a required dependency for bup, so the package you got was not good. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 465491] Kup on daily interval schedule - no backup after suspend
https://bugs.kde.org/show_bug.cgi?id=465491 --- Comment #1 from Simon Persson --- Thanks for the report! Very clear. I will need to look into how the process sleep is handled across suspension, I think I had tested that and it worked back long ago when I worked on that part of kup. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Buckups won't run, no errors given.
https://bugs.kde.org/show_bug.cgi?id=453919 --- Comment #7 from Simon Persson --- Had some time to look at this one now. I think the problem could be line 111 of edexecutor.cpp. https://invent.kde.org/system/kup/-/blob/master/daemon/edexecutor.cpp#L111 That should be mkpath instead of mkdir. I don't have a computer to test it on, would appreciate of someone could try to make that change, test and report. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Backup folder not created for external disk plans
https://bugs.kde.org/show_bug.cgi?id=453919 Simon Persson changed: What|Removed |Added Summary|Buckups won't run, no |Backup folder not created |errors given. |for external disk plans -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374450] DATA LOSS: Saving a file can overwrite other file
https://bugs.kde.org/show_bug.cgi?id=374450 --- Comment #2 from Simon Persson --- I have now upgraded my installation to version 5.4.0 and the behaviour has not changed, still a problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374450] New: DATA LOSS: Saving a file can overwrite other file
https://bugs.kde.org/show_bug.cgi?id=374450 Bug ID: 374450 Summary: DATA LOSS: Saving a file can overwrite other file Product: digikam Version: 5.3.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: showfoto Assignee: digikam-de...@kde.org Reporter: simon.pers...@mykolab.com Target Milestone: --- Steps to reproduce: 1. Open folder with photos using the "open folder" button. 2. Select a photo to edit by double-clicking on it in the thumbbar. 3. Make some edit to the photo. 4. Select another photo in the thumbbar, single click only. 5. Click "Save". The problem is that the modified photo is now written to the filename of the current selection in the thumbbar, overwriting the contents of that file. I assume this is not the intended function, at least I found it very unexpected. This happened to me several times, each time I noticed the data loss I restored the overwritten photo from backup and continued editing other photos. Then it happened again, and again. Took me a long time to understand what was going on. -- You are receiving this mail because: You are watching all bug changes.
