Page 1 of 1
keepassx error
Posted: 16 Aug 2017, 17:52
by Ed_P
keepassx-0.4.4-x86_64-1gv.xzm
Continued from:
USM bug reports
What am I doing wrong??
Code: Select all
guest@porteus:~$ keepassx
keepassx: error while loading shared libraries: libQtXml.so.4: cannot open shared object file: No such file or directory
guest@porteus:~$ locate libQtXml.so.4
locate: warning: database /var/lib/slocate/slocate.db' is more than 8 days old
locate: fatal error: search_db: open: '/var/lib/slocate/slocate.db': Permission denied
guest@porteus:~$ su
Password:
root@porteus:/home/guest# updatedb
root@porteus:/home/guest# locate libQtXml.so.4
/usr/lib/libQtXml.so.4
/usr/lib/libQtXml.so.4.8
/usr/lib/libQtXml.so.4.8.2
/usr/lib/libQtXml.so.4.8.5
/usr/lib/qt/lib/libQtXml.so.4
/usr/lib/qt/lib/libQtXml.so.4.8
/usr/lib/qt/lib/libQtXml.so.4.8.2
/usr/lib/qt/lib/libQtXml.so.4.8.5
root@porteus:/home/guest# ln -s /usr/lib/libQtXml.so.4 libQtXml.so.4
root@porteus:/home/guest# keepassx
keepassx: error while loading shared libraries: libQtXml.so.4: cannot open shared object file: No such file or directory
root@porteus:/home/guest#
keepassx error
Posted: 16 Aug 2017, 18:35
by Blaze
Ed_P,
Code: Select all
root@porteus:~# ldd /usr/bin/keepassx
linux-vdso.so.1 (0x00007ffdc4ca4000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f0742ea6000)
libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007f0742ca0000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0742a81000)
libQtXml.so.4 => not found
libQtGui.so.4 => not found
libQtCore.so.4 => not found
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f0742700000)
libm.so.6 => /lib64/libm.so.6 (0x00007f07423ad000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f0742196000)
libc.so.6 => /lib64/libc.so.6 (0x00007f0741db7000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f0741b92000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f074198f000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f074178a000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f0741586000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f0741374000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f0741164000)
/lib64/ld-linux-x86-64.so.2 (0x00007f07431e1000)
root@porteus:~# ldd /usr/bin/keepassx
linux-vdso.so.1 (0x00007ffd16d9a000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fbea4489000)
libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007fbea4283000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fbea4064000)
libQtXml.so.4 => /usr/lib64/qt/lib/libQtXml.so.4 (0x00007fbea3e1c000)
libQtGui.so.4 => /usr/lib64/qt/lib/libQtGui.so.4 (0x00007fbea3123000)
libQtCore.so.4 => /usr/lib64/qt/lib/libQtCore.so.4 (0x00007fbea2c28000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fbea28a7000)
libm.so.6 => /lib64/libm.so.6 (0x00007fbea2554000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007fbea233d000)
libc.so.6 => /lib64/libc.so.6 (0x00007fbea1f5e000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fbea1d39000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fbea1b36000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fbea1931000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fbea172d000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fbea151b000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fbea130b000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbea47c4000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007fbea1109000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007fbea0df8000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007fbea0bc6000)
libz.so.1 => /lib64/libz.so.1 (0x00007fbea09af000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fbea06fd000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fbea04ab000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007fbea02a4000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007fbea0089000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fbe9fe7f000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fbe9fc3c000)
librt.so.1 => /lib64/librt.so.1 (0x00007fbe9fa34000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fbe9f7c2000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007fbe9f52d000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fbe9f31d000)
libffi.so.6 => /usr/lib64/../lib64/libffi.so.6 (0x00007fbe9f115000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fbe9ef11000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007fbe9ece7000)
root@porteus:~#
I installed only these packages
keepassx-0.4.4-x86_64-1gv.txz and
qt-4.8.7-x86_64-6.txz
keepassx error
Posted: 16 Aug 2017, 20:06
by donald
Hi Ed
Blaze's solution is the easiest - imo
I may add some tips how to troubleshoot those kind of problems.
Boot stock porteus and install e.g. keepassx,
if it doesn't start open a terminal and try to start the programm.
It will show what is missing - libQtXml.so.4 in this case iirc
Now search the system (find/locate etc) if you already have this file/library.
If no, additional package(s) containing this file are needed (usm -s library name)
If yes, the file/library is most likely located in a folder/path were the
programm doesn't look for it.(hence not found)
Now there are 2 ways to go:
1) place a link to the library (if already present) in the folder/path where
the program does look for it.(usually /usr/lib or /usr/lib64 etc)
2) If you can't find out the correct path, install the additional module which
make the program run and compare where the (needed) libraries are now beeing
placed/linked to.
This will show you where to place the links if the files/libraries have been
present - but in the wrong location - before.
Link the library into the correct folder/path - start the program again (in terminal)
It will show you if the library is found now, and/or something else is missing now..
keepassx error
Posted: 16 Aug 2017, 20:15
by Ed_P
Thank you
Blaze.
So we are kinda back to why didn't USM attach that required package when building the keepassx module.
Also with the qt module you mentioned USM shows many additional packages required. How many did you include in your module?
-update-
I downloaded the file from our link and converted it to xzm. Keepassx now works with 3.2.2.
keepassx error
Posted: 16 Aug 2017, 20:22
by donald
seems that USM did know the files are already there - but keepassx can not find them.
usr/lib64/
qt/lib/libQtXml.so.4
keepassx error
Posted: 16 Aug 2017, 20:39
by Ed_P
donald wrote: ↑16 Aug 2017, 20:22
seems that USM did know the files are already there - but keepassx can not find them.
usr/lib64/
qt/lib/libQtXml.so.4
I don't think so. Without the
Blaze qt module:
Code: Select all
guest@porteus:~$ ls /usr/lib64/qt/lib/
/bin/ls: cannot access '/usr/lib64/qt/lib/': No such file or directory
guest@porteus:~$
And as the tale continues, I tried to open my keepass database with the new functioning keepassx module and it fails with "Wrong Signature".
keepassx error
Posted: 16 Aug 2017, 20:56
by Ed_P
Thank you for this
donald.
donald wrote: ↑16 Aug 2017, 20:06
Hi Ed
Blaze's solution is the easiest - imo
If you mean downloading the module he linked to I agree.
I may add some tips how to troubleshoot those kind of problems.
Boot stock porteus and install e.g. keepassx,
if it doesn't start open a terminal and try to start the programm.
It will show what is missing - libQtXml.so.4 in this case iirc
Yup, did these steps.
Now search the system (find/locate etc) if you already have this file/library.
I tend to assume USM does this when downloading modules.
If no, additional package(s) containing this file are needed (usm -s library name)
Ok. Do you see the qt file
Blaze recommended?
Code: Select all
guest@porteus:~$ su
Password:
root@porteus:/home/guest# usm -s libQtXml.so.4
-----------------------------
Are you searching for a library file?
libQtXml.so.4, it seems a library.
Would you like to find the package for it? [y/n]
libQtXml.so.4 was found in copasi-4.20.158-x86_64-1_slonly.txz
root@porteus:/home/guest#
If yes, the file/library is most likely located in a folder/path were the
programm doesn't look for it.(hence not found)
Now there are 2 ways to go:
1) place a link to the library (if already present) in the folder/path where
the program does look for it.(usually /usr/lib or /usr/lib64 etc)
2) If you can't find out the correct path, install the additional module which
make the program run and compare where the (needed) libraries are now beeing
placed/linked to.
This will show you where to place the links if the files/libraries have been
present - but in the wrong location - before.
Link the library into the correct folder/path - start the program again (in terminal)
It will show you if the library is found now, and/or something else is missing now..
And that's where things get complicated.
keepassx error
Posted: 16 Aug 2017, 22:57
by donald
Ed ... just for you..
--Porteus 3.2.2 cinnamon 64 Bit--
Download / activate
keepassx-0.4.4-x86_64-1gv.xzm
copasi-4.20.158-x86_64-1_slonly.xzm
libpng-legacy12-1.2.57-x86_64-1_slonly.xzm
in terminal do
Code: Select all
root@porteus:/home/guest# cd /usr/lib64
root@porteus:/usr/lib64# ln -s /usr/share/copasi/lib/libQtXml.so.4 libQtXml.so.4
root@porteus:/usr/lib64# ln -s /usr/share/copasi/lib/libQtGui.so.4 libQtGui.so.4
root@porteus:/usr/lib64# ln -s /usr/share/copasi/lib/libQtCore.so.4 libQtCore.so.4
done..
keepassx error
Posted: 17 Aug 2017, 02:50
by Ed_P
I appreciate the followup
donald but I don't understand the purpose.
I appear to have the links you propose.
Code: Select all
guest@porteus:~$ ls /usr/lib64/libQt*
/usr/lib64/libQt3Support.so@
/usr/lib64/libQt3Support.so.4@
/usr/lib64/libQt3Support.so.4.8@
/usr/lib64/libQt3Support.so.4.8.7@
/usr/lib64/libQtCLucene.so@
/usr/lib64/libQtCLucene.so.4@
/usr/lib64/libQtCLucene.so.4.8@
/usr/lib64/libQtCLucene.so.4.8.7@
/usr/lib64/libQtCore.so@
/usr/lib64/libQtCore.so.4@
/usr/lib64/libQtCore.so.4.8@
/usr/lib64/libQtCore.so.4.8.7@
/usr/lib64/libQtDBus.so@
/usr/lib64/libQtDBus.so.4@
/usr/lib64/libQtDBus.so.4.8@
/usr/lib64/libQtDBus.so.4.8.7@
/usr/lib64/libQtDeclarative.so@
/usr/lib64/libQtDeclarative.so.4@
/usr/lib64/libQtDeclarative.so.4.8@
/usr/lib64/libQtDeclarative.so.4.8.7@
/usr/lib64/libQtDesigner.so@
/usr/lib64/libQtDesigner.so.4@
/usr/lib64/libQtDesigner.so.4.8@
/usr/lib64/libQtDesigner.so.4.8.7@
/usr/lib64/libQtDesignerComponents.so@
/usr/lib64/libQtDesignerComponents.so.4@
/usr/lib64/libQtDesignerComponents.so.4.8@
/usr/lib64/libQtDesignerComponents.so.4.8.7@
/usr/lib64/libQtGui.so@
/usr/lib64/libQtGui.so.4@
/usr/lib64/libQtGui.so.4.8@
/usr/lib64/libQtGui.so.4.8.7@
/usr/lib64/libQtHelp.so@
/usr/lib64/libQtHelp.so.4@
/usr/lib64/libQtHelp.so.4.8@
/usr/lib64/libQtHelp.so.4.8.7@
/usr/lib64/libQtMultimedia.so@
/usr/lib64/libQtMultimedia.so.4@
/usr/lib64/libQtMultimedia.so.4.8@
/usr/lib64/libQtMultimedia.so.4.8.7@
/usr/lib64/libQtNetwork.so@
/usr/lib64/libQtNetwork.so.4@
/usr/lib64/libQtNetwork.so.4.8@
/usr/lib64/libQtNetwork.so.4.8.7@
/usr/lib64/libQtOpenGL.so@
/usr/lib64/libQtOpenGL.so.4@
/usr/lib64/libQtOpenGL.so.4.8@
/usr/lib64/libQtOpenGL.so.4.8.7@
/usr/lib64/libQtScript.so@
/usr/lib64/libQtScript.so.4@
/usr/lib64/libQtScript.so.4.8@
/usr/lib64/libQtScript.so.4.8.7@
/usr/lib64/libQtScriptTools.so@
/usr/lib64/libQtScriptTools.so.4@
/usr/lib64/libQtScriptTools.so.4.8@
/usr/lib64/libQtScriptTools.so.4.8.7@
/usr/lib64/libQtSql.so@
/usr/lib64/libQtSql.so.4@
/usr/lib64/libQtSql.so.4.8@
/usr/lib64/libQtSql.so.4.8.7@
/usr/lib64/libQtSvg.so@
/usr/lib64/libQtSvg.so.4@
/usr/lib64/libQtSvg.so.4.8@
/usr/lib64/libQtSvg.so.4.8.7@
/usr/lib64/libQtTest.so@
/usr/lib64/libQtTest.so.4@
/usr/lib64/libQtTest.so.4.8@
/usr/lib64/libQtTest.so.4.8.7@
/usr/lib64/libQtWebKit.so@
/usr/lib64/libQtWebKit.so.4@
/usr/lib64/libQtWebKit.so.4.10@
/usr/lib64/libQtWebKit.so.4.10.4@
/usr/lib64/libQtXml.so@
/usr/lib64/libQtXml.so.4@
/usr/lib64/libQtXml.so.4.8@
/usr/lib64/libQtXml.so.4.8.7@
/usr/lib64/libQtXmlPatterns.so@
/usr/lib64/libQtXmlPatterns.so.4@
/usr/lib64/libQtXmlPatterns.so.4.8@
/usr/lib64/libQtXmlPatterns.so.4.8.7@
guest@porteus:~$
keepassx error
Posted: 17 Aug 2017, 03:13
by Ed_P
Disabled the qt module and added the two you recommended.
Code: Select all
guest@porteus:~$ ls /usr/lib64/libQt*
/bin/ls: cannot access '/usr/lib64/libQt*': No such file or directory
guest@porteus:~$ cd /usr/lib64
guest@porteus:/usr/lib64$ ln -s /usr/share/copasi/lib/libQtXml.so.4 libQtXml.so.4
ln: failed to create symbolic link 'libQtXml.so.4': Permission denied
guest@porteus:/usr/lib64$ su
Password:
root@porteus:/usr/lib64# ln -s /usr/share/copasi/lib/libQtXml.so.4 libQtXml.so.4
root@porteus:/usr/lib64# ln -s /usr/share/copasi/lib/libQtGui.so.4 libQtGui.so.4
root@porteus:/usr/lib64# ln -s /usr/share/copasi/lib/libQtCore.so.4 libQtCore.so.4
root@porteus:/usr/lib64# ls /usr/lib64/libQt*
/usr/lib64/libQtCore.so.4@ /usr/lib64/libQtXml.so.4@
/usr/lib64/libQtGui.so.4@
root@porteus:/usr/lib64# keepassx
Qt: Session management error: None of the authentication protocols specified are supported
root@porteus:/usr/lib64#
And trying to open my KeePass.kdbx file still resulted in a KeePass Wrong Signature error.
keepassx error
Posted: 17 Aug 2017, 03:33
by donald
Ed, you have them now, but you wouldn't have them with stock porteus.
(no additional modules activated)
You have activated other (Qt) modules in the meantime, right?
So this is simply a description of how to get "keepassx" to work in (stock) porteus.
EDIT
run keepassx as guest in terminal ( or from shortcut in menu)
--> KeePass Wrong Signature error <--
this might be a security feature, so no one can open your database copied/stolen
from your PC -- there might be a signature file somewhere or a database
export/import option, i don't know..
(Otherwise only paper and pencil remains)
EDIT 2
the whole story:
Boot porteus 3.2.2 cinnamon 64
download/activate keepassx - doesn't work > start keepassx in terminal (guest)
and it can't find libQtXml.so.4
seach for libQtXml.so.4 reveals you need "copasi" > download/activate this one >
"keepassx" still not working - same message "it can't find libQtXml.so.4" >
(because they are in usr/share/copasi/lib/ but have to be in /usr/lib64)
link this one - message gone but "it can't find libQtGui.so.4" > link this one -
message gone but "it can't find libQtCore.so.4" > link this one message gone but
it also want libpng12. (porteus has 14 and 16 but not 12) > search libpng 12 >
is in package "libpng-legacy12" download/activate > no error in terminal and
keepassx starts, also from shortcut in menu.
That's the whole adventure.
keepassx error
Posted: 17 Aug 2017, 04:43
by Ed_P
Oh, but the adventure continues.
Booted old netbook's Porteus RazorQt 3.0.1 system. Ran it's keepassx app and it works, just like before, able to signon and view entries no problem
It's working with an older version of the keepass database, kdb rather than kdbx. And note the DE's name, no need for a Qt module.
Back to the new notebook. Booted Windows, ran KeePass, exported the kdbx database to a kdb file, booted Porteus Cinnamon 3.2.2, dbl clicked on the kdb file, invoked keepassx, entered password and Voila!!
I suspect when I was running Porteus 3.0 there was no keepass module for kdbx files so I had to create a kdb backup file for the keepass module that was available. Now that USM shows KeePass 2.x versions I will have to try using one of them. In that their sizes vary from 500K to 9820K any suggestion on which one(s) to try?
BTW I admire and appreciate your help and patience with this
donald.
keepassx error
Posted: 17 Aug 2017, 05:28
by Ed_P
The 736K keepassx-2.0.3-x86_64-1alien module works with the keepass.kdbx file.
keepassx error
Posted: 17 Aug 2017, 08:19
by Blaze
Ed_P wrote: ↑16 Aug 2017, 20:15
How many did you include in your module?
Only
keepassx-0.4.4-x86_64-1gv.txz and
qt-4.8.7-x86_64-6.txz
keepassx error
Posted: 17 Aug 2017, 14:26
by Ed_P