[SOLVED] libgtop-2.30.0-1 no longer contains libgtop-2.0.so.7?

Question

Hey All,
I use Psensor and it seems it requires libgtop-2.0.so.7 but when I check to see if I have libgtop installed, it says that I do.
Has the updated version of the software stopped creating this wonderful shared object file? And if so, what temperature monitoring devices do you guys recommend? I do love my Psensor though... T_T
Last edited by MutantJohn (2014-06-04 07:04:49)

Answer 1

There might still be some issues with the PKGBUILD
From namcap
$ namcap psensor-0.8.0.6
psensor-0.8.0.6-1-x86_64.pkg.tar.xz psensor-0.8.0.6.tar.gz
[user@arch ~/build/psensor]$ namcap psensor-0.8.0.6-1-x86_64.pkg.tar.xz
psensor E: Files in /usr/share/icons/hicolor but no call to gtk-update-icon-cache or xdg-icon-resource to update the icon cache
psensor W: Description should not contain the package name.
psensor W: File (usr/etc/) exists in a non-standard directory.
psensor W: File (usr/etc/xdg/) exists in a non-standard directory.
psensor W: File (usr/etc/gconf/) exists in a non-standard directory.
psensor W: File (usr/etc/gconf/schemas/) exists in a non-standard directory.
psensor W: File (usr/etc/gconf/schemas/psensor.schemas) exists in a non-standard directory.
psensor W: File (usr/etc/xdg/autostart/) exists in a non-standard directory.
psensor W: File (usr/etc/xdg/autostart/psensor.desktop) exists in a non-standard directory.
psensor W: Dependency libgtop detected but optional (libraries ['usr/lib/libgtop-2.0.so.10'] needed in files ['usr/bin/psensor'])
psensor W: Dependency libnotify detected but optional (libraries ['usr/lib/libnotify.so.4'] needed in files ['usr/bin/psensor'])
psensor W: Dependency json-c detected but optional (libraries ['usr/lib/libjson-c.so.2'] needed in files ['usr/bin/psensor'])
psensor W: Dependency curl detected but optional (libraries ['usr/lib/libcurl.so.4'] needed in files ['usr/bin/psensor'])
psensor W: Dependency libatasmart detected but optional (libraries ['usr/lib/libatasmart.so.4'] needed in files ['usr/bin/psensor'])
psensor W: Dependency included and not needed ('help2man')
and from the makepkg install
make[3]: Entering directory '/home/user/build/psensor/src/psensor-0.8.0.6/src'
/usr/bin/mkdir -p '/home/user/build/psensor/pkg/psensor/usr/bin'
/usr/bin/install -c psensor '/home/user/build/psensor/pkg/psensor/usr/bin'
GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule ../src/psensor.schemas
(gconftool-2:3985): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Attached schema `/schemas/apps/psensor/graph/alpha_channel_enabled' to key `/apps/psensor/graph/alpha_channel_enabled'
WARNING: failed to install schema `/schemas/apps/psensor/graph/alpha_channel_enabled', locale `C': Unable to store a value at key '/schemas/apps/psensor/graph/alpha_channel_enabled', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections — put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf