[frameworks-activities-stats] [Bug 487385] plasma crashed in KAStatsFavoritesModel::Private::trigger when removing a duplicated discover entry from favorites
https://bugs.kde.org/show_bug.cgi?id=487385 Ivan Čukić changed: What|Removed |Added CC||alexander.loh...@gmx.de, ||ivan.cu...@kde.org --- Comment #7 from Ivan Čukić --- The only thing I can think this could come from is an off by one error that results in the last item being repeated somehow (we used to have duplicates - the same thing with different URIs specified, but I think that was fixed during 5.x). Alexander, do you have any idea what could be the cause of this? (tagging you as the last one who edited this function) p.s. this is code in plasma-workspace/applets/kicker/plugin/kastatsfavoritesmodel.cpp - handles favourites in a plasma-customized way so the assigned product is a it off, but that is not that important. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485895] Error loading Vaults
https://bugs.kde.org/show_bug.cgi?id=485895 --- Comment #1 from Ivan Čukić --- Is it possible that the issue is in the installation? I don't see this problem on Artix (Arch + OpenRC). Updating the system now, will see if it breaks with the latest. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485151] Correct password won't open vault as destination is "not empty"
https://bugs.kde.org/show_bug.cgi?id=485151 --- Comment #2 from Ivan Čukić --- cryfs' high memory requirements are by design since at least 2020 - see https://github.com/cryfs/cryfs/issues/335#issuecomment-652338744 Now, the question I have is how do the 'not empty' and 'cryfs killed' results relate to each other? Does one happen the first time, and the other one the second time you try it, or something else? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 485051] Remove EncFS from the list of supported Algorithms
https://bugs.kde.org/show_bug.cgi?id=485051 Ivan Čukić changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Ivan Čukić --- The issues with encfs are important for the user to know about, and for that reason Vaults shows the information about the issues. The problems the audit pointed out relate to using encfs in a situation where the encrypted data is synced to a remote data storage that the attacker has access to. If encfs is used locally only, the encryption it has is good enough. Apart from the message about the security of encfs, an additional deterrent of using it with online syncing is that you can not choose the location of the encrypted data storage when using encfs as the backend. After the recent news with xz, I'm starting to think that the fact we don't have a new version of encfs is a good thing - we have a version that has been audited and for which we know the faults and when it should and shouldn't be used. For the things that have active development, an audit (if they have been audited at all) quickly becomes obsolete and new patches might worsen the security. :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 483063] Unable to detect cryfs/encfs/encfsctl/gocryptfs version - cannot create a vault
https://bugs.kde.org/show_bug.cgi?id=483063 --- Comment #1 from Ivan Čukić --- Hi, Do you have cryfs, encfs or gocryptfs installed, and available in your $PATH? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 472633] vault lost all data
https://bugs.kde.org/show_bug.cgi?id=472633 --- Comment #3 from Ivan Čukić --- Looks like you put the wrong directory in the cryfs command - it should not be the path to the location where vault shows the data when opened, but the path to encrypted data. If you didn't change the default path when creating the vault, it will be in your home directory under ~/.local/share/plasma-vault/ Apart from getting the path from plasmavaultrc, you can also find all directories where cryfs keeps its data by doing (this will search only under your user's home directory): find ~ -name 'cryfs.config' > when I did the apt upgrade, it was open and had some security and > firmware updates, could it have some relevance? An update should not have an influence over the user data. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 472633] vault lost all data
https://bugs.kde.org/show_bug.cgi?id=472633 --- Comment #1 from Ivan Čukić --- Vault doesn't handle the data, the only way for the data to disappear is if they were deleted or there was a filesystem corruption. I'd try to mount the cryfs manually - see the relevant paths in the .config/plasmavaultrc The location of the encrypted data is the path in square brackets. For example, [/home/user/.vaults/SomeVaultName.enc]. First, backup that directory somewhere just in case. After that, do this: mkdir /tmp/SomeVaultName cryfs /home/user/.vaults/SomeVaultName.enc /tmp/SomeVaultName If you get an error saying something about the filesystem needs to be upgraded, call cryfs --allow-filesystem-upgrade /home/user/.vaults/SomeVaultName.enc /tmp/ SomeVaultName If that doesn't help (it should mount the data into /tmp/SomeVaultName) post me the error message you got. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 468189] Browsing opened big Vault (6Gb) is really slow especially with Dolphin and its Open file dialog
https://bugs.kde.org/show_bug.cgi?id=468189 --- Comment #5 from Ivan Čukić --- Yes, gocryptfs is the main contender for the next default. Encfs has issues which make it unsuitable for cloud syncing*. But is generally good enough for local use. *) With a note that there are some enterprise end-to-end encryption solutions which are worse than encfs. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 468189] Browsing opened big Vault (6Gb) is really slow especially with Dolphin and its Open file dialog
https://bugs.kde.org/show_bug.cgi?id=468189 --- Comment #3 from Ivan Čukić --- The current plan is to replace it as the default and revert the patch that hides the backend selection combo box. Back when it was made the default, we didn't know of its downsides - nothing similar happened during my tests. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 468189] Browsing opened big Vault (6Gb) is really slow especially with Dolphin and its Open file dialog
https://bugs.kde.org/show_bug.cgi?id=468189 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Ivan Čukić --- cryfs can be really slow. The command runs in the background, so `time` doesn't really measure anything except how much time it takes for cryfs to load the encryption key for later access. I'd switch to gocryptfs or even encfs (if you are not syncing the encrypted directory to a remote server). -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 467083] Incredibly large memory amounts are needed to open vaults
https://bugs.kde.org/show_bug.cgi?id=467083 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #3 from Ivan Čukić --- Thanks for reporting this. I guess it is time to rethink the backends and whether to have a default... I like cryfs security-wise, but it was a pain point for a few times now... -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 465763] The installation folder can not be changed
https://bugs.kde.org/show_bug.cgi?id=465763 Ivan Čukić changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 457478] Incorrect warning [clazy-fully-qualified-moc-types] about ActionReply
https://bugs.kde.org/show_bug.cgi?id=457478 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/sdk/ ||clazy/commit/18d37db546744f ||629d13414cfd390f74958a2ba0 --- Comment #2 from Ivan Čukić --- Git commit 18d37db546744f629d13414cfd390f74958a2ba0 by Ivan Čukić, on behalf of Ilya Pominov. Committed on 07/02/2023 at 23:24. Pushed by ivan into branch 'master'. Fix clazy-fully-qualified-moc-types check for ActionReply ActionReplay in KAuth must be without namespace M +5-0src/checks/level0/fully-qualified-moc-types.cpp https://invent.kde.org/sdk/clazy/commit/18d37db546744f629d13414cfd390f74958a2ba0 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 464617] Uncrypted Folder in Vaults
https://bugs.kde.org/show_bug.cgi?id=464617 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #12 from Ivan Čukić --- > how can i support you (like send a like or rate you ) because you did it Heh, no need, glad we could sort this out :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 464617] Uncrypted Folder in Vaults
https://bugs.kde.org/show_bug.cgi?id=464617 --- Comment #8 from Ivan Čukić --- What editor do you like? KWrite, Kate, ...? Just open any text editor you like - go to File -> Open in the menu, and open ~/.config/plasmavaultrc You will see the file grouped into sections. Each section defines data for one vault, and the format is something like this (it has more fields than this, and the order is not important): [/path/where/the/encrypted/data/is/stored] name=Name of the Vault backend=cryfs mountPoint=/path/where/the/vault/data/is/shown/when/vault/is/unlocked Apart from these, you should also have a section named [EncryptedDevices] If you want to remove a specific vault from the applet, remove the section that defines it, and remove it from the [EncryptedDevices] section. After you restart the system, the vault should be removed from the applet. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 464617] Uncrypted Folder in Vaults
https://bugs.kde.org/show_bug.cgi?id=464617 --- Comment #5 from Ivan Čukić --- edit - not a command, open ~/.config/plasmavaultrc file in an editor and edit the file. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 464617] Uncrypted Folder in Vaults
https://bugs.kde.org/show_bug.cgi?id=464617 --- Comment #3 from Ivan Čukić --- No need to download anything again - just log out and log in again. Editing plasmavaultsrc just removes the vaults from the applet, nothing else. (ofc, it is always good to make backups just in case before doing anything like this) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 464617] Uncrypted Folder in Vaults
https://bugs.kde.org/show_bug.cgi?id=464617 --- Comment #1 from Ivan Čukić --- I guess the safest way (the most manual way) to remove it is the following: killall kded5 edit ~/.config/plasmavaultrc and remove all the vaults you don't want to have anymore clean up / delete all the relevant directories (remember the paths you deleted from the rc file) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464250] Activities order is a mess
https://bugs.kde.org/show_bug.cgi?id=464250 Ivan Čukić changed: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #4 from Ivan Čukić --- Fair enough, moving to pager component then. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464250] Activities order is a mess
https://bugs.kde.org/show_bug.cgi?id=464250 Ivan Čukić changed: What|Removed |Added Target Milestone|--- |1.0 Status|RESOLVED|REPORTED Product|kactivitymanagerd |plasmashell CC||h...@kde.org Component|general |Pager Resolution|INTENTIONAL |--- Assignee|ivan.cu...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 464250] Activities order is a mess
https://bugs.kde.org/show_bug.cgi?id=464250 Ivan Čukić changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Ivan Čukić --- Activities list in the default switcher are in the most-recently-used order - like windows in alt-tab switcher. This is intentional. If someone wants to create an option to reorder this, with it being false by default, I'd be fine with it. Until someone does, resolving issue as intentional. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 444814] Cryptomator backend
https://bugs.kde.org/show_bug.cgi?id=444814 --- Comment #2 from Ivan Čukić --- Two downsides of cryptomator: - No packages in most important distributions - Debian, Ubuntu, openSUSE (available user-created packages for some) - Java-based - Java applications are notorious for being sensitive to the user environment -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 462314] Feature suggestion: Provided information about back-ends could be viewed even if that back-end isn't installed
https://bugs.kde.org/show_bug.cgi?id=462314 Ivan Čukić changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Ivan Čukić --- I agree -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 459961] Improve "move to activity" feature.
https://bugs.kde.org/show_bug.cgi?id=459961 --- Comment #4 from Ivan Čukić --- There's this page on how to get involved with contributing to documentation: https://community.kde.org/Get_Involved/documentation I'm afraid that the docs format and the workflow are not what people would expect today. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 459961] Improve "move to activity" feature.
https://bugs.kde.org/show_bug.cgi?id=459961 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ivan Čukić --- IMO, this is the main way to move windows: https://phabricator.kde.org/D29548 (was a bit improved since that commit - it now allows moving and adding to) The documentation is always lacking unfortunately, we rarely get people that like writing it. The 'move to' should have been added to the window (alt+f3) menu when it was added to the context menu of the taskbar, so I'm marking this as confirmed. The key shortcuts would be also a nice idea. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 459959] Improve activities documentation
https://bugs.kde.org/show_bug.cgi?id=459959 Ivan Čukić changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 458356] Plasma 5.25.x not launching on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=458356 --- Comment #13 from Ivan Čukić --- Were you able to check if kwin and plasma are running somehow in different environments? I'm not a BSD guy, I can't really help there. You could patch plasma to log somewhere the list of dbus services it sees after the message that kamd is not found for debugging purposes. To see why it thinks kamd is not there. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 456705] clazy-standalone -p drops first argument
https://bugs.kde.org/show_bug.cgi?id=456705 Ivan Čukić changed: What|Removed |Added Assignee|unassigned-b...@kde.org |ivan.cu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 456705] clazy-standalone -p drops first argument
https://bugs.kde.org/show_bug.cgi?id=456705 Ivan Čukić changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 456705] clazy-standalone -p drops first argument
https://bugs.kde.org/show_bug.cgi?id=456705 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||ivan.cu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 459288] Uses lots of CPU power
https://bugs.kde.org/show_bug.cgi?id=459288 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Ivan Čukić --- Hi, can you list the sizes of the files in database directory? How big is the wal file? We've had no problems with sqlite for years, and the latest versions just went berserk... -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 459191] Plasma Crashes in KActivities::Stats::ResultModel::ResultModel()
https://bugs.kde.org/show_bug.cgi?id=459191 Ivan Čukić changed: What|Removed |Added Resolution|FIXED |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Ivan Čukić --- > #11 0x7fa19a594726 in QSqlDatabase::addDatabase(QString const&, QString > const&) () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 Maybe the Qt update fixed the issue as the assert was in Qt itself. I'll close this, and if it happens again, please reopen and add the terminal output. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 458356] Plasma 5.25.x not launching on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=458356 --- Comment #10 from Ivan Čukić --- Ok, so it is functioning properly, is just plasma that doesn't see it from what I can tell. When you're in a window like Konsole, press Alt+F3 to show the KWin menu, do you have the activities submenu there? The only time when I saw something similar to this was when somehow one application had access to one dbus service, and another application to another dbus service, so they didn't see each other. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 458356] Plasma 5.25.x not launching on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=458356 --- Comment #7 from Ivan Čukić --- What does it mean kactivitymanagerd is running 'in the broken state'? Are you able to run qdbus org.kde.ActivityManager /ActivityManager/Activities ListActivities and get something? If you got the result, and you do qdbus org.kde.ActivityManager /ActivityManager/Activities AddActivity "TestActivity" does ListActivities return one item more? If all these work, try out kactivities-cli --list-activities and see if it gives a normal output. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 459191] Plasma Crashes in KActivities::Stats::ResultModel::ResultModel()
https://bugs.kde.org/show_bug.cgi?id=459191 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #1 from Ivan Čukić --- Can you post the terminal output of plasmashell as this is some assert? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Ivan Čukić changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #34 from Ivan Čukić --- @medin thanks for reporting back! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #31 from Ivan Čukić --- @Sebastian Schuberth The USB use-case is a practical one and it will most likely happen after I do the Vault refactor that is in works. Though, for USBs, I'd advise full-disk-encryption instead of using Vaults (cryptsetup-based). But I guess creating an encrypted drive can be more tedious than using a Vault. @Carlo For cloud stuff sync (apart from the downsides you mentioned), doing a sync of encrypted data means that all your devices share the same encryption key (not only the passphrase, but the internal key used by the encryption algorithm). Now, cryfs author did design it with cloud in mind, so I might be overly restrictive here... I guess a nicer (and public) import mechanism could be added along with removable devices support. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #30 from Ivan Čukić --- Hi medin, First, I'd create a backup of the encrypted data just in case. Next, mount the vault manually from terminal. BACKEND_COMMAND ABSOLUTE_PATH_TO_ENCRYPTED_DATA WHERE_YOU_WANT_TO_MOUNT Depending on which backend you used to create the vault, BACKEND_COMMAND will be cryfs, encfs or gocryptfs. So, for example, if you used encfs and your vault data is in /home/user/.local/share/plasma-vault/VaultName.enc and you want to mount it to /home/user/vaults/VaultName, you'd do this: encfs /home/user/.local/share/plasma-vault/VaultName.enc /home/user/vaults/VaultName You'll be able to access the unlocked data in /home/user/vaults/VaultName. You can copy the data somewhere (for example, to a new Vault you created). To close/unmount the vault, just do fusermount -u /home/user/vaults/VaultName If you want to test out the (hidden) import feature, after all of the steps above (including the call to fusermount -u), do: qdbus org.kde.kded5 /modules/plasmavault requestImportVault And go through the steps of importing the vault. Please report back if it worked. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 454000] current activity information doesn't change
https://bugs.kde.org/show_bug.cgi?id=454000 --- Comment #5 from Ivan Čukić --- - Does Plasma react to activity change? - What do you get when you try to change the current activity via dbus? - What do you get when you list all activities via dbus? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457731] Vault still appears in list after deleting it
https://bugs.kde.org/show_bug.cgi?id=457731 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457680] if offline vault is open during shot down, system will start with vault closed but still offline
https://bugs.kde.org/show_bug.cgi?id=457680 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Ivan Čukić --- Yes, this happens because it is not Vault that closes the mount, but the system shutdown. Fixing this would require Vault to store the 'network is disabled due to Vault' somewhere on the drive - to know that it should enable the network on next boot. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457368] Suggestion for adding the feature of panic firewall mode on
https://bugs.kde.org/show_bug.cgi?id=457368 Ivan Čukić changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #6 from Ivan Čukić --- @Emanuele Ok, cool. Will see what we can do here :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457368] Suggestion for adding the feature of panic firewall mode on
https://bugs.kde.org/show_bug.cgi?id=457368 --- Comment #1 from Ivan Čukić --- Can you explain the difference to killing all the connections? (I've never used firewalld) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 438070] CLI interface
https://bugs.kde.org/show_bug.cgi?id=438070 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Ivan Čukić --- Hi, There are two CLI-only commands that the Vault supports that were introduced for nice integration with KDE Connect [1]: qdbus org.kde.kded5 /modules/plasmavault closeAllVaults qdbus org.kde.kded5 /modules/plasmavault forceCloseAllVaults qdbus org.kde.kded5 /modules/plasmavault closeVault qdbus org.kde.kded5 /modules/plasmavault forceCloseVault Opening vaults from CLI is problematic. Communicating the password between the CLI command and the Vaults service would be insecure. This might be doable in a secure way if the CLI command cloned the whole logic of GUI Vaults, but this would need some non-password synchronization between different things that are allowed to open vaults. This would need to be thought through and will result in significant refactor / reimplementation. The good part of this potential refactor, if I manage to prove it doesn't open new vectors of attack, is that it would allow Plasma to show password fields inline in the Vault applet instead of them being shown in a separate window owned by a random process (KDED). I'll mark this as assigned. [1] https://cukic.co/2018/04/14/plasma-vault-with-kde-connect-and-more/ -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Ivan Čukić changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 --- Comment #18 from Ivan Čukić --- Thanks, will try to set it up in a VM to see whether I can reproduce it on Arch. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 --- Comment #16 from Ivan Čukić --- Also, what is the content of .local/share/kactivitymanagerd/resources/errors.log ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 --- Comment #15 from Ivan Čukić --- Still haven't been able to reproduce the issue. I'm working on a health checker that will disable adding recent documents to the database if the wal file becomes larger than the database itself. But that is not a proper fix for the issue. Are you all on Arch? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 --- Comment #3 from Ivan Čukić --- > Never should grow that much, but in fact I met such huge file, what described. Yes, I believe you, just meant to say that this is really unexpected. On a properly working sqlite, WAL should not be bigger than the DB itself. :) Do you use anything out of the ordinary which might keep the database locked so that WAL can not be flushed? Or some uncommon plasma applets, or strange filesystems (NFS being a common problem)? Does the following return anything other than plasmashell, kactivitymanagerd? lsof | grep /home/YOUR_USER_NAME/.local/share/kactivitymanagerd/resources/database > Maybe there is an option in configuration of sqlite which limits size of log > file, > if so then would be nice to set it. There is, but it doesn't really do anything. There is some work on a new WAL system, but that doesn't help us now. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416271] Setting to not remember recent documents confusingly lives in the Activities KCM
https://bugs.kde.org/show_bug.cgi?id=416271 Ivan Čukić changed: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #5 from Ivan Čukić --- If we collected a few toggles related to privacy, we could have a 'privacy centre' item in the system tray. For example: - disable usage tracking for the current activity - forget recent usage history - allow network searches in KRunner - ... I don't see another plausible solution - putting a 'forget' menu into everything that shows recents, plus a button somewhere close to allow discretely 'forgetting' (https://bugs.kde.org/show_bug.cgi?id=353229) would be quite a UI problem. > and the bugginess of the implementation. Off topic: Almost all bugs we have had over the years (since plasma 4 days) are due to people storing non-normalized URIs in KA or changing format of the URIs between versions thinking KA will magically know that konsole, applications:Konsole, applications:/Konsole.desktop.whatever, /usr/share/...desktop are the same thing. I was thinking of changing the API to force the user to set the allowed URI format before allowing reporting URIs, but that would just make it more difficult to make mistakes, not impossible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353229] Impossible to "forget recent documents" discreetly
https://bugs.kde.org/show_bug.cgi?id=353229 --- Comment #14 from Ivan Čukić --- @Nate that bug report I agree with - it is not discoverable. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 453468] Opening plasma vault fails with error code 127
https://bugs.kde.org/show_bug.cgi?id=453468 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #4 from Ivan Čukić --- Omer, thanks for triaging this! Peter, you can also try to compile cryfs from scratch. These issues usually happen when incompatible versions of some library are used. I marked this as a downstream issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353229] Impossible to "forget recent documents" discreetly
https://bugs.kde.org/show_bug.cgi?id=353229 Ivan Čukić changed: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #11 from Ivan Čukić --- Not a fan of the use-case, but... :) This is possible to a certain extent via System Settings -> Workspace Behavior -> Activities -> Privacy -> Clear History where you can choose to forget the last hour or more. For custom time intervals, you could use this from terminal: qdbus org.kde.ActivityManager /ActivityManager/Resources/Scoring DeleteRecentStats ':usedActivity' 5 h -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 453570] activitymanagerd created database which took 80 GB in file system
https://bugs.kde.org/show_bug.cgi?id=453570 Ivan Čukić changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Ivan Čukić --- The wal file is sqlite's write-ahead log. It should never grow that much. Will see what can be done about it. In the early days, sqlite gave us a few headaches, but nothing recently. Esp nothing of this magnitude... :/ As for the notification, the default plasma setup notifies on low space on any hard drive. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 453550] kactivitymanagerd flood logs with "Linking" entries
https://bugs.kde.org/show_bug.cgi?id=453550 --- Comment #5 from Ivan Čukić --- A possibility would be to launch plasmashell from terminal (and enable logging kdebugdialog5 before that) to see the logs. I expect those will be visible there. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 453550] kactivitymanagerd flood logs with "Linking" entries
https://bugs.kde.org/show_bug.cgi?id=453550 --- Comment #1 from Ivan Čukić --- Can you post the plasma logs so that we can tell what tries to add the favourite so often? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449563] System Settings Quick Settings page shows same "Most Used" item twice
https://bugs.kde.org/show_bug.cgi?id=449563 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|plasma-b...@kde.org |ivan.cu...@kde.org --- Comment #10 from Ivan Čukić --- Hi Schlaefer, Can you post the output of the following here (as two attachments). sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'select * from ResourceScoreCache where initiatingAgent = "org.kde.systemsettings";' and sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'select * from ResourceEvent where initiatingAgent = "org.kde.systemsettings";' I see two possible causes of this -- plasma changed how it reports KCM URLs (but the kcm: prefix wasn't added in 5.24) or, as you said, some other component reporting this the wrong way. This is not something that KActivities can handle, but we can prune the invalid ones easily when they are loaded in system settings. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 452070] gocryptfs doesn't mount on dolphin like cryfs or encfs
https://bugs.kde.org/show_bug.cgi?id=452070 --- Comment #3 from Ivan Čukić --- @Nate - this is a 15 minute bug :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 452070] gocryptfs doesn't mount on dolphin like cryfs or encfs
https://bugs.kde.org/show_bug.cgi?id=452070 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Ivan Čukić --- It is a solid thing. Will be fixed soon. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 452040] Allow storing on pcloud drive
https://bugs.kde.org/show_bug.cgi?id=452040 --- Comment #1 from Ivan Čukić --- No idea what pcloud is, but if it is some kind of a virtual filesystem, vault can not work with it. If you can create a sync form some local directory to pcloud, you can create the encrypted part of the vault in that directory and sync to pcloud. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 452039] Password length plasma-vault
https://bugs.kde.org/show_bug.cgi?id=452039 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #3 from Ivan Čukić --- Which backend are you using for the vault? cryfs, encfs or gocryptfs -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 451452] Auto suspend activities on idle time
https://bugs.kde.org/show_bug.cgi?id=451452 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Ivan Čukić --- This is an interesting idea to be honest. We'll see what will happen with this part of activities (the application session management) in Plasma 6 as people want to remove it, but let's keep this one 'confirmed'. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451209] Highlights are meant to be drawn as backgrounds, not on top of other items.
https://bugs.kde.org/show_bug.cgi?id=451209 Ivan Čukić changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/com ||mit/bb2bc5827f43dfce8f217b7 ||c4370acaec0dca032 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Ivan Čukić --- Git commit bb2bc5827f43dfce8f217b7c4370acaec0dca032 by Ivan Čukić. Committed on 06/03/2022 at 22:15. Pushed by carlschwan into branch 'master'. Calendar: Draw highlight below the text The highlight is drawn on top of the day which makes the text not visible when the users use themes in which the highlight is not mostly transparent. This sets z order of the highlight to -1 which makes it painted below the text. M +1-0src/declarativeimports/calendar/qml/DayDelegate.qml https://invent.kde.org/frameworks/plasma-framework/commit/bb2bc5827f43dfce8f217b7c4370acaec0dca032 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451209] Highlights are meant to be drawn as backgrounds, not on top of other items.
https://bugs.kde.org/show_bug.cgi?id=451209 Ivan Čukić changed: What|Removed |Added Assignee|plasma-b...@kde.org |ivan.cu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451209] Highlights are meant to be drawn as backgrounds, not on top of other items.
https://bugs.kde.org/show_bug.cgi?id=451209 Ivan Čukić changed: What|Removed |Added Status|REPORTED|ASSIGNED CC||ivan.cu...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 446437] Applet misleadingly says "no vaults have been set up" instead of a real error message when kded module wasn't loaded is or crashing
https://bugs.kde.org/show_bug.cgi?id=446437 --- Comment #2 from Ivan Čukić --- Is vault kded module crashing or ...? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 446250] Vault failed if mount dir is not empty and display a misleading message.
https://bugs.kde.org/show_bug.cgi?id=446250 --- Comment #2 from Ivan Čukić --- What backend are you using? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 446051] Vaults not recognized after changing username
https://bugs.kde.org/show_bug.cgi?id=446051 Ivan Čukić changed: What|Removed |Added Status|REPORTED|ASSIGNED Summary|Vault not recognized after |Vaults not recognized after |upgrade |changing username Ever confirmed|0 |1 --- Comment #3 from Ivan Čukić --- Some FUSE modules don't like relative paths, so this would need to be handled by Vault. I'm trying to keep the 'smart' functionality to a minimum - to keep the attack surface as small as possible. I'll have to think about $HOME and whether it can be used to trick the user somehow. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 446051] Vault not recognized after upgrade
https://bugs.kde.org/show_bug.cgi?id=446051 --- Comment #1 from Ivan Čukić --- Hi, The paths are stored as absolute paths in $HOME/.config/plasmavaultrc so that is the place you need to update them. Advised approach: killall kded5 edit the file - replace all /home/OLD_USERNAME with /home/NEW_USERNAME kded5 This should do the trick. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 445542] If Dolphin is open in another Activity, the vault opens in that Activity even if it's configured to only stay open in the current Activity, thus immediately locking it.
https://bugs.kde.org/show_bug.cgi?id=445542 Ivan Čukić changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-vault/commit/9626 ||e0d94208c0135da4ca79f4fa39f ||42a16117a Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Ivan Čukić --- Git commit 9626e0d94208c0135da4ca79f4fa39f42a16117a by Ivan Čukić. Committed on 16/11/2021 at 08:57. Pushed by ivan into branch 'ivan/open-new-dolphin-window'. Request a new dolphin window when opening vaults M +22 -4kded/service.cpp https://invent.kde.org/plasma/plasma-vault/commit/9626e0d94208c0135da4ca79f4fa39f42a16117a -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 442831] Add option to disable opening vault's mount point upon unlocking
https://bugs.kde.org/show_bug.cgi?id=442831 --- Comment #1 from Ivan Čukić --- There is the 'Unlock Vault' action which is shown when you click the vault (or the triangle/arrow thingie on the right) which does not open Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 442642] [Widget] Use inline password field
https://bugs.kde.org/show_bug.cgi?id=442642 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Ivan Čukić --- This is a nice idea. But as the things currently stand, this can not be done without inter-process communication, and I don't want the password to be sent between processes for security reasons. (Vault is held to a higher security requirements than NM) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #8 from Ivan Čukić --- No need. If this happens again, then I'll annoy them ;) Thanks -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 Ivan Čukić changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Ivan Čukić --- Should be fixed by https://invent.kde.org/plasma/plasma-vault/-/merge_requests/16 -- for 5.23 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #5 from Ivan Čukić --- This is the reason I didn't want to support gocryptfs at first, as it didn't have the --version standardized (depends on how it was compiled, it could even be empty). When we got the patch for adding gocryptfs to Vault, I was told this has been fixed in gocryptfs since then. I'll fix this, but I expect it to break again at some point... -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 436290] Opening vault is really slow even with small data
https://bugs.kde.org/show_bug.cgi?id=436290 --- Comment #4 from Ivan Čukić --- Please report back if gocryptfs is up to the task. I liked the way cryfs is developed, and how open the author is to requests, but this would be a second big plus for making gocryptfs the default in Vault. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 436290] Opening vault is really slow even with small data
https://bugs.kde.org/show_bug.cgi?id=436290 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Ivan Čukić --- CryFS has some performance issues. This should be reported upstream again. There is currently an open bug report for large volumes [1] where the comment was that it might be slow because cryfs splits everything into 32k files (though, on my system it looks like the default is 16k). This could, I guess, be a valid reason for large volumes to be slow, but not for the small ones. It could be a solution to use the gocryptfs backend instead (had no slowness reports in Vault yet for that one), or encfs if you don't plan to sync the data to a cloud (I'm using encfs for ages now for several large volumes without any issues). @dauntless Vaults have been designed to cover many-small-encrypted-containers instead of the one-huge-container use-case. If you want to keep all files on an encrypted drive, I'd advise to go for full-disk encryption or something like Tomb [2]. At some point, I created a Tomb backend for Vaults, but never merged it as Tomb requires some interaction with sudo which is a problem I haven't found a satisfying solution to yet except forcing the user to edit sudoers to allow running sudo tomb without entering a password. [1] https://github.com/cryfs/cryfs/issues/346 [2] https://www.dyne.org/software/tomb/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435647] Application Menu's Favorite Icons disappear after reboot
https://bugs.kde.org/show_bug.cgi?id=435647 Ivan Čukić changed: What|Removed |Added Component|general |Application Launcher ||(Kickoff) Target Milestone|--- |1.0 CC||mikel5...@gmail.com Assignee|ivan.cu...@kde.org |k...@davidedmundson.co.uk Product|kactivitymanagerd |plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #13 from Ivan Čukić --- KWin/Wayland does not still have the activities support as far as I know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435356] History fails to include some recently used apps
https://bugs.kde.org/show_bug.cgi?id=435356 Ivan Čukić changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|ivan.cu...@kde.org |h...@kde.org Product|kactivitymanagerd |plasmashell Component|general |Application Menu (Kicker) --- Comment #6 from Ivan Čukić --- This is intentional extra-filtering done by Kicker, moving back to plasmashell and assigning to Eike. applets/kicker/plugin/recentusagemodel.cpp:105 return (service && (!favoritesModel || !favoritesModel->isFavorite(service->storageId(; -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434637] Another way to switch activities
https://bugs.kde.org/show_bug.cgi?id=434637 --- Comment #3 from Ivan Čukić --- No :) I guess the confusion is that Gnome took the term 'activities' and used it for something else to Plasma so people coming from Gnome have a bit of a hard time. The Alt-Tab thing is 'task switcher' and is configurable - just go to System Settings -> Window Management -> Task Switcher and test out different visualisations. New ones can be downloaded via 'Get New Task Switchers', though those are not /that/ different to those stock ones. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434637] Another way to switch activities
https://bugs.kde.org/show_bug.cgi?id=434637 --- Comment #1 from Ivan Čukić --- Can you post a screenshot? Activity switcher does not show window previews. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 434463] Vaults hides vaults on NTFS partition
https://bugs.kde.org/show_bug.cgi?id=434463 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Ivan Čukić --- The reason for this behaviour was 'disable on first error' to avoid tampering. But I agree this refresh would be quite useful (I don't expect performance issues) and not that problematic security-wise. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 405035] Provide "Switch to next/previous activity" actions
https://bugs.kde.org/show_bug.cgi?id=405035 --- Comment #4 from Ivan Čukić --- You can define shortcuts that traverse activities in alphabetical order here: System Settings -> Shortcuts -> Plasma -> Switch to Next Activity and Switch to Previous Activity Mind that these switch activities without the 'alt+tab' effect of showing the activity switcher. The shortcuts 'Walk through activities' traverse them in most recently used order. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 433994] Password field loses focus
https://bugs.kde.org/show_bug.cgi?id=433994 Ivan Čukić changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 433459] Plasma Vault doesn't work with cryfs 0.11.0 (git version)
https://bugs.kde.org/show_bug.cgi?id=433459 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Ivan Čukić --- While we don't support unreleased software, this report is extremely useful so that we can get prepared for the next cryfs release. Thanks! Seems the development version of cryfs has an issue working in an empty environment (cleaned up environment variables which is something vault does for safety reasons - we don't want someone injecting something into the environment to change the behaviour of cryfs behind our backs) I've opened an upstream issue report: https://github.com/cryfs/cryfs/issues/374 I'm not going to mark this as resolved/upstream until this is either fixed upstream, or here if the upstream doesn't ant to fix this. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)
https://bugs.kde.org/show_bug.cgi?id=410457 --- Comment #6 from Ivan Čukić --- This will be a wall of text with some potential future hope at the end ;) > Why is this not a use-case for plasma-vault? The use-case for Plasma Vault, as said before, is to provide 'safe' containers on top of the usual protections available in Linux. > This makes no sense because the default backend (cryfs) The answer here is two-fold. Vault is not meant to be a do-all UI for cryfs or gocryptfs (otherwise, there would be no point in creating Vaults when Sirikali exists). Vault is a system for [[see first paragraph]] that uses well established encryption mechanisms like cryfs and gocryptfs to implement the [[see first paragraph]]. Now, I have nothing against syncing the encrypted data to the cloud. That part does not collide with Vaults use-case. What does collide with Vaults use-case is keeping Vaults open for long periods of time. As a real-world analogy, imagine a Plasma Vault is a wall safe where people keep their valuables. You just don't keep the wall safe open for as long as you are at home, and you don't keep the access code written on a paper in your office. To make the analogy complete wrt the cloud, when you move houses, you don't will not mind the safe being transfered from one house to another without your supervision (assuming it is unbreakable and unstealable without the access code) but safe transfer is not really the reason *why* you got the safe in the first place. > While I think this would be an interesting project, it doesn't fit my > use case. My cloud is a simple file storage. I know. The reason I mentioned git+gpg is that it is as easy to open a gitlab/github/... account as dropbox. I do agree it can be a hassle since most users already have dropbox or something similar. But it would provide quite a more portable (non-vendor-locked) solution to the same problem of end-to-end encryption. Portable in the sense that changing a provider would be trivial (be it an existing git provider, or just a random server that you have ssh access to - that does not even have to have a git server installed on it). > Also as mentioned before, this is not the solution for my use-case. > The only thing I want to prevent is that the people having access to > the server my data is stored on can not read it unencrypted. > > Encrypting home will bring zero benefit for this. Since the cloud sync > software runs under my user after login, it will see the decrypted files > and so upload them unencrypted. This does not help at all in this use-case. Let me explain what I meant. If you set up home encryption using something like cryfs as the backend (so, FUSE-based like Vault, not FDE), you'll have a directory /home/.myuser.enc (for example) and /home/myuser. The fact that /home/myuser is mounted and the data is accessible does not stop you from syncing /home/.myuser.end to the cloud. So encrypted data is the only thing that is transmitted over the network. This does not even need to be a full home encryption, it can be a normal directory /home/myuser/Dropbox/_encrypted_data which you set to be mounted on login to /home/myuser/MySecureDocuments. > Also, implementing a "save password" option would be good for consistency. > > Plasma does already support saving the password for for example external > encrypted disks / storage. Now imagine the cloud as another "external > storage" since it is exactly this. > > It would make sense for plasma to be consistent and support the same > functionality (in this case saving the password) for all encrypted > external storages the same. Consistency *is* important. But, still, less important than security and privacy. At least for Vault. To be honest, and this is not me being facetous, if I wanted to enforce consistency, I'd rather remove the password saving for encrypted drives than add it to Vaults. If KWallet (and alternatives) were safe, I would probably consider allowing password storage. > Linux and Plasma are all about freedom and giving the options. > To refuse users use-cases seems off in this philosophy. Uh, this old chestnut. :) This is not true. Plasma and KDE software do provide a lot of configuration options to the user, but this is not our philosophy. Especially not when privacy and security are concerned. We've been under some fire over the years because of this (running UI apps as root, html messages in kmail, ...) but while I do like to be able to configure everything in general, I (and most of KDE devs) would never put configurability over security and privacy. > Nobody will be force to use this option when it is there, so it > won't hurt anyone, but only help some :) Sadly, this is not true. Most people don't understand cryptography well. (heck, most developers don't - there are 'enterprise' end-to-end encrypted cloud solutions that use worse encrypti
[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)
https://bugs.kde.org/show_bug.cgi?id=410457 Ivan Čukić changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Ivan Čukić --- To repeat, if you want encryption just for the cloud sync, which is unlocked while you're logged in, Vault is not the solution. It is not Vault's use-case. Vault is *not* going to support use-cases which blur the best practices for its use-case. One of the interesting things I've been researching recently (which might end up as a new KDE project at one point) is git+gpg which provides a nice end-to-end encryption. The local files are not encrypted, but they are sent properly encrypted to a git server. This would be a good tool for your use-case. As mentioned before, the alternative is to set up the usual encrypted $HOME (or some other directory) and sync the encrypted data with your cloud provider. This would have the benefit of gpg+git with added protection against device theft if it is stolen while powered off. P.S. Bug status is meant for developers to classify bugs. While we all appreciate the discussion, there is no point in reopening a bug unless a developer reopens it because the discussion made them see the problem in a different light. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)
https://bugs.kde.org/show_bug.cgi?id=410457 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Ivan Čukić --- There are already better tools for this use-case. You should encrypt user's home directory, or better, create an encrypted /home partition. The same goes for PAM - if you want encryption that integrates with login, Vault is not the solution. Integration with KWallet is out of the question as it would render Vaults useless. Anyone who has access to a computer with the user logged in would have access to all Vaults as getting the password from KWallet is as simple as invoking a single command in shell. There is no point in keeping something encrypted if the encryption key is easily accessible. Vaults are meant and designed to be small encrypted containers _under_ your regular security (be it a simple login or an encrypted drive etc.) that are in the locked state for as much as they can be. That is the reason closing a vault can be easily done and easily automated (activit switching, kde connect commands) while requiring an explicit action to open them. As for cloud storage, the encrypted data can be synced without the vault being open. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #11 from Ivan Čukić --- Hm, I don't like that it is ok with a clean user. Means that some setting in kwin can hide this. If you figure out what was the problem or how to reproduce, please report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #6 from Ivan Čukić --- Is it possible that kwin on arch is compiled without development headers of kactivities? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 430058] Several seconds of random lag in UI
https://bugs.kde.org/show_bug.cgi?id=430058 --- Comment #3 from Ivan Čukić --- Hi Steve, Those files are automatically handled by sqlite. WAL is a write-ahead-log - a technique sqlite uses to avoid updating the database for each sql insert/update command. It writes the updates to WAL and then merges a chunk of them at once. KAMD only tells sqlite to flush WAL every 400k instead of the default 4M. Now, sqlite is free to ignore this request - it flushes only if the flush can be fast enough. So, the WAL file can grow more than that. This code (in KAMD) hasn't really been changed in 5 years. Did freebsd get a new version of sqlite recently? Now, Inkscape and KAMD have nothing in common - if KAMD manages to slow down Inkscape, my guess is that the OS doesn't handle file writes as it should. Maybe Inkscape is also trying to write something to the hard drive. Can you watch whe process IO with iotop to see what KAMD and Inkscape do when you experience the slowdown. Also, can you track the RAM usage while this happens? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 430881] Icon title consumes too much space (at least in Russian translation)
https://bugs.kde.org/show_bug.cgi?id=430881 Ivan Čukić changed: What|Removed |Added Component|general |ru CC||ivan.cu...@kde.org, ||kekc...@gmail.com Assignee|aa...@kde.org |aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 430881] Icon title consumes too much space (at least in Russian translation)
https://bugs.kde.org/show_bug.cgi?id=430881 Ivan Čukić changed: What|Removed |Added Assignee|ivan.cu...@kde.org |aa...@kde.org Status|REPORTED|CONFIRMED Product|Plasma Vault|i18n Ever confirmed|0 |1 Component|general |general --- Comment #1 from Ivan Čukić --- Moving to i18n as this is (IMO) a translation problem. I'd say the translation is overly literal - almost as translating Plasma as "системный пользовательский интерфейс" everywhere instead of using the product name. The product name is Vault. It could be translated to Russian as сейф. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428085] "Often Used/Recent file" list doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=428085 Ivan Čukić changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Ivan Čukić --- > not yet landed and its commit will be different. It has, and the commit that fixes the issue is the one linked (it was a merge, not a rebase, so the sha is preserved) Fix to be released in 5.77 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428085] "Often Used/Recent file" list doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=428085 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kactivities-stats/co ||mmit/6faad8ed5f76510de06707 ||836d6406e7177086a3 --- Comment #7 from Ivan Čukić --- Git commit 6faad8ed5f76510de06707836d6406e7177086a3 by Ivan Čukić. Committed on 19/11/2020 at 17:39. Pushed by ivan into branch 'ivan/event-filtering-for-files-and-directories'. Add event filtering for files and directories The df52b1a3 revision introduced Type::files and Type::directories special resource type values for queries, but it omitted to support the same special values in the ResultWatcher. M +10 -1src/resultwatcher.cpp https://invent.kde.org/frameworks/kactivities-stats/commit/6faad8ed5f76510de06707836d6406e7177086a3 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 411900] Tracking activity
https://bugs.kde.org/show_bug.cgi?id=411900 --- Comment #2 from Ivan Čukić --- This is something that kinda existed in Plasma 4.x (for Plasma Active) when kactivitymanagerd followed a 'let's add everything into it' kind of an application. KAMD grew too much to be maintainable, so the scope is now more focussed. I agree that this would be a great thing to have in Plasma, but not as a part of KAMD. A separate time tracking application / plasma applet / system tray applet that integrates with activities* would be quite easy to implement. If anyone is game, I could mentor the project. At least the activities integration part. * Plasma Vault was also in a sense a part of KAMD in Plasma Active days, and now it is a separate applet that integrates with activities. And, IMO, much better than what we had back then. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Ivan Čukić --- @Albert Great, thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
