Announcement

Collapse
No announcement yet.

Keepass 2 not working in Kubuntu 20.04 beta.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Try installing it from the CLI. As you already have it installed via Discover, in the konsole type: sudo apt install --reinstall keepass2
    Using Kubuntu Linux since March 23, 2007
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #17
      Originally posted by Snowhog View Post
      Try installing it from the CLI. As you already have it installed via Discover, in the konsole type: sudo apt install --reinstall keepass2
      OK I tried that and here's what happened:


      sudo apt install --reinstall keepass2
      [sudo] password for mktest:
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      The following packages were automatically installed and are no longer required:
      libykpers-1-1 libyubikey-udev libyubikey0 libzxcvbn0
      Use 'sudo apt autoremove' to remove them.
      Suggested packages:
      keepass2-doc mono-dmcs xdotool
      The following NEW packages will be installed:
      keepass2
      0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
      Need to get 0 B/1,433 kB of archives.
      After this operation, 3,557 kB of additional disk space will be used.
      Selecting previously unselected package keepass2.
      (Reading database ... 174367 files and directories currently installed.)
      Preparing to unpack .../keepass2_2.44+dfsg-1_all.deb ...
      Unpacking keepass2 (2.44+dfsg-1) ...
      Setting up keepass2 (2.44+dfsg-1) ...
      Processing triggers for mime-support (3.64ubuntu1) ...
      Processing triggers for hicolor-icon-theme (0.17-2) ...
      Processing triggers for man-db (2.9.1-1) ...
      Processing triggers for shared-mime-info (1.15-1) ...
      Processing triggers for desktop-file-utils (0.24-1ubuntu2) ...

      It still wont launch so I tried the terminal again keepass2 and here's what happened:

      keepass2

      (cli:2456): Gtk-WARNING **: 18:31:15.298: Unable to locate theme engine in module_path: "adwaita",
      System.ArgumentException: A null reference or invalid value was found [GDI+ status: InvalidParameter]
      at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x0009b] in <728fbd68fe594062895e1f819791e76a>:0
      at System.Drawing.Bitmap..ctor (System.Int32 width, System.Int32 height, System.Drawing.Imaging.PixelFormat format) [0x00017] in <728fbd68fe594062895e1f819791e76a>:0
      at System.Drawing.Bitmap..ctor (System.Drawing.Image original, System.Int32 width, System.Int32 height) [0x00000] in <728fbd68fe594062895e1f819791e76a>:0
      at System.Drawing.Bitmap..ctor (System.Drawing.Image original, System.Drawing.Size newSize) [0x00010] in <728fbd68fe594062895e1f819791e76a>:0
      at (wrapper remoting-invoke-with-check) System.Drawing.Bitmap..ctor(System.Drawing.Image,S ystem.Drawing.Size)
      at System.Windows.Forms.XplatUIX11.DefineCursor (System.Drawing.Bitmap bitmap, System.Drawing.Bitmap mask, System.Drawing.Color cursor_pixel, System.Drawing.Color mask_pixel, System.Int32 xHotSpot, System.Int32 yHotSpot) [0x0004e] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.XplatUI.DefineCursor (System.Drawing.Bitmap bitmap, System.Drawing.Bitmap mask, System.Drawing.Color cursor_pixel, System.Drawing.Color mask_pixel, System.Int32 xHotSpot, System.Int32 yHotSpot) [0x00000] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.Cursor.CreateCursor (System.IO.Stream stream) [0x00058] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.Cursor..ctor (System.Type type, System.String resource) [0x00021] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.Cursors.get_SizeNWSE () [0x0001a] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.SizeGrip..ctor (System.Windows.Forms.Control CapturedControl) [0x00006] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at (wrapper remoting-invoke-with-check) System.Windows.Forms.SizeGrip..ctor(System.Windows .Forms.Control)
      at System.Windows.Forms.ScrollableControl.CreateScrol lbars () [0x000c2] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.ScrollableControl..ctor () [0x000b0] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.ContainerControl..ctor () [0x0000e] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at System.Windows.Forms.Form..ctor () [0x00012] in <a3daa9b84fd241a497578a25f68bc3c7>:0
      at KeePass.Forms.MainForm..ctor () [0x00143] in <15a3c3813eee42a48d65caee98f0310e>:0
      at (wrapper remoting-invoke-with-check) KeePass.Forms.MainForm..ctor()
      at KeePass.Program.MainPriv (System.String[] args) [0x00681] in <15a3c3813eee42a48d65caee98f0310e>:0

      Comment


        #18
        keepass2 runs fine on my 19.10 setup, it seems


        Click image for larger version

Name:	Screenshot_20200413_201911.jpg
Views:	1
Size:	35.4 KB
ID:	644635

        Comment


          #19
          Originally posted by claydoh View Post
          keepass2 runs fine on my 19.10 setup, it seems

          [ATTACH=CONFIG]8738[/ATTACH]
          Are you using VirtualBox? And if so what version?
          Because I'm using version 5. And this is a problem for me on both Kubuntu version 19.10 and 20.04 beta.

          Comment


            #20
            Just created an Oracle VirtualBox (Version 5.2.38) VM of 20.04 using todays daily download. Installed keepass2: sudo apt install keepass2

            When it finished, I closed the Konsole and launched the application from KRunner by clicking on the Desktop and typing keepass2 and pressing Enter. It launches without error.
            Using Kubuntu Linux since March 23, 2007
            "It is a capital mistake to theorize before one has data." - Sherlock Holmes

            Comment


              #21
              Originally posted by SuperSapien64 View Post
              Are you using VirtualBox? And if so what version?
              Because I'm using version 5. And this is a problem for me on both Kubuntu version 19.10 and 20.04 beta.

              VB 6, I see no reason to run the older version, though I am not sure how it would make a difference, unless the issue is perhaps video related, as 6 has a much better virtual gpu than 5, imo.

              your terminal output does not show any actual errors as far as I can tell. My instance has no output in Konsole.

              Comment


                #22
                Originally posted by claydoh View Post
                VB 6, ... , as 6 has a much better virtual gpu than 5, imo.
                I have not had success running VB 6 on my iMac with regards to the desired VM window size, and that even when Guest Additions has been installed. I have no such problems running the 5x series.
                Using Kubuntu Linux since March 23, 2007
                "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                Comment


                  #23
                  Weird I just installed Kubuntu 18.04.4 in VB and I'm having the same issue with KeePass2.
                  Note: On my desktop I have Kubuntu 18.04.4 installed and I'm not having any issues with KeePass2 there, just on VB.

                  Comment


                    #24
                    Hmm I just tried running Kubuntu 18.04.4 in VB version 6 on Windows 10 on the same desktop and I was able to launch KeePass2 just fine. So maybe I should try VB version 6. If I uninstall VB from the Discover Software Center will lose any of my VMs?

                    Comment


                      #25
                      You don't need to uninstall VB. If you download/install VB 6, it will detect that VB 5 is installed and remove it before installing VB 6. Existing VMs are not affected.
                      Using Kubuntu Linux since March 23, 2007
                      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                      Comment


                        #26
                        Originally posted by Snowhog View Post
                        You don't need to uninstall VB. If you download/install VB 6, it will detect that VB 5 is installed and remove it before installing VB 6. Existing VMs are not affected.
                        I tried to install VB v 6 and it didn't replace version 5 so I had to uninstall it from the Discover Software Center and it looks like it no working properly. I get error messages whenever I try launch a VM it reads failed to open a session for virtual machine then a system error that says:

                        RTR3InitEx failed with rc=-1912 (rc=-1912)

                        The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

                        '/sbin/vboxconfig'

                        may correct this. Make sure that you are not mixing builds of VirtualBox from different sources.

                        where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

                        Comment


                          #27
                          You need to do what the error message instructs you to do:

                          run the command
                          Code:
                          sudo /sbin/vboxconfig
                          Which will rebuild the needed kernel modules for the new version.

                          Comment


                            #28
                            Originally posted by claydoh View Post
                            You need to do what the error message instructs you to do:

                            run the command
                            Code:
                            sudo /sbin/vboxconfig
                            Which will rebuild the needed kernel modules for the new version.
                            I tried that and it didn't help here's what happened after I entered the command:

                            sudo /sbin/vboxconfig
                            [sudo] password for mlka:
                            vboxdrv.sh: Stopping VirtualBox services.
                            vboxdrv.sh: Starting VirtualBox services.

                            Comment


                              #29
                              I'm wondering if I should try this?
                              Code:
                              sudo apt-get remove --purge virtualbox


                              https://askubuntu.com/questions/7037...ove-virtualbox

                              Comment

                              Working...
                              X