![]() ![]()
In contrast, KeePassXC is hosted on GitHub, development is done out in the open, and it's trivial to see that in just the last year there were. Similarly, the website is ancient and doesn't seem to have kept up with the times I seem to recall it was only recently that it even got HTTPS support. #Keeweb webdav 304 error how to#As a result I'm not really sure how to gauge the level of activity on the project itself. #Keeweb webdav 304 error code#The seems to be an outdated SVN repo which was last updated in 2009, and I don't see any description of how to contribute code to the project anywhere. KeePass 2 seems to still be hosted on Sourceforge, and I'm not even sure where to get a copy of the latest (non-release) version of the source. As last step, you need to restart your gnome shell or restart your computer to apply the changes in the system.I'm strongly considering it just based on the community surrounding each project. Your file should like this after the modification: In this file, you need to modify the executable parameter ( Exec), adding the -no-sandbox flag to the launcher: Exec=keeweb -no-sandbox %u You can then modify it through the terminal using nano (alternatively modify it with your favorite text editor): sudo nano ~/.local/share/applications/sktop desktop file to the current user's applications directory: cp /usr/share/applications/sktop ~/.local/share/applications However, it isn't recommended to modify this file directly as it will be rewritten by updates, so it's better to copy the. Now, assuming that it worked for you, launching a terminal and letting it open isn't that practical in a desktop environment, it should work out of the box by simply clicking on the Keeweb icon isn't? That's why you need to modify the unity launcher of Keeweb to adjust that, the file should be located in the following path /usr/share/applications/sktop. We highly recommend that you only use this flag for testing purposes, and never in production. You can also disable Chromium's sandbox entirely with the -no-sandbox CLI flag, which will disable the sandbox for all processes (including utility processes). This comes with security risks, especially if any untrusted code or content is present in the unsandboxed process. In certain use cases that are incompatible with the sandbox (for instance, when using native node modules in the renderer), it is possible to disable the sandbox for specific processes. According to the official documentation of Electron Framework:įor most apps, sandboxing is the best choice. Temporary solution (until Keeweb receives an update)Īlthough no the ideal solution, it is for sure the quickest solution to launch the application in your system is to launch it through the terminal with an additional parameter, namely -no-sandbox: keeweb -no-sandboxĪfter running this command the application should be launched without any problem. ![]() This issue was solved in the official electron project already, the problem is that the latest version of Keeweb doesn't use a newer version of Electron (the issue is still open on Github), causing the problem of the application in many of the latest operative systems based in Linux such as Arch Linux, Ubuntu, Fedora etc. The issue is caused specifically because of the version of Electron Framework used on the project that contains a bug where it makes applications crash in with glibc 2.34. ![]() #Keeweb webdav 304 error windows#Electron Framework is the choice of many developers for packing web based applications as desktop applications that run on Linux, macOS and Windows using the same codebase. usr/bin/keeweb: line 2: 17607 Trace/breakpoint trap (core dumped) /usr/share/keeweb-desktop/keeweb " "Īfter some research, I found out that the problem wasn't Keeweb directly, but the platform where it runs on, Electron. Libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Then, I tried to launch the application from the terminal and that's when I found the following error: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) At the beginning, I thought that maybe there was a problem with the way I installed Keeweb, so instead of using sudo apt-get, I used dpkg -i, with no success. I've always used Keeweb for Ubuntu, however during the installation of this program in Ubuntu 22.04, the application simply didn't start when clicking the icon. I usually store all of my credentials in keepass files as this allows me to store and use secure passwords for every account I have on the internet in a very safe way. This means that you can use it to manage your keepass files in other environment that isn't Windows. #Keeweb webdav 304 error password#Keeweb is an awesome free cross-platform desktop application password manager compatible with KeePass. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |