Closed hannes08 closed 4 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.96. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Hi @hannes08 that is very unfortunate.
I'd like to ask a couple of questions to help in debugging this issue.
1) What OS are you using ? It would really help if I knew this was a Windows, macOS or Linux thing since all three handle files and folders a bit differently 😉
2) Are you using QtPass with "native" gpg support or via pass
?
3) Do you have git
support enables?
This changes a lot of file manipulation behaviour.
Sorry I forgot to mention! :-)
On drag and drop of a password the same isse arises (it's moved pyhiscally, staged in git but not committed or pushed). Side note: on moving, all passwords in destination folder will be reencrypted, but these changes are neither staged nor committed nor pushed.
Time for operation: No OS Left Behind
Since most issues on macOS and Linux/BSD now seem fixed . . it's once again time for me to dive into the wonderful world of Windows 🕺
I had a similar issue ... when renaming password QtPass removes .gpg
and they disappear from the UI. I have to rename them manually and commit them.
Arch Linux, qtpass 1.3.2
Same as @schmunk42 using: Fedora 31, qtpass 1.3.2-1.fc31
Getting the same problem as @schmunk42. Using Ubuntu 18.04 with fresh compile of master as of yesterday.
Also unable to delete a folder and i'm getting:
fatal: pathspec '/absolutepathtothefoldertodelete/' did not match any files
Where absolutepathtothefoldertodelete is the absolute path of the folder to delete, not a literal from the error.
Side note: when compiling i have to comment out the qmake automatic file naming of your translation files from main/main.cpp:
Q_INIT_RESOURCE(qmake_qmake_qm_files); // qmake names the file
otherwise it fails with unable to resolve qmake_qmake_qm_files
Regards, Matt
+1 for @schmunk42, same issue on Windows 10, qtpass v1.3.2 I'm also commenting here because I believe that issue #520 is related to this.
I don't use Git integration and I don't have native Pass installed.
On renaming of a directory: fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths Git status shows an uncommited but staged change for the folder
On renaming of a file: fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths Git status shows an uncommited but staged change for the file. The file is unencrypted!