By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2274 - Klipper tdeinit_klipper.so missing
Summary: Klipper tdeinit_klipper.so missing
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: debian (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: R14.0.1
  Show dependency tree / graph
 
Reported: 2014-12-25 12:41 CST by Markus Raab
Modified: 2015-07-08 12:56 CDT (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Raab 2014-12-25 12:41:39 CST 
Klipper does not start because shared library tdeinit_klipper.so is missing.

Problem likely is a packaging problem in debian wheezy.

apt-file inidicates that no package provides that .so.
Comment 1 Slávek Banko 2014-12-25 12:45:17 CST 
# dpkg -S /opt/trinity/lib/libtdeinit_klipper.so
klipper-trinity: /opt/trinity/lib/libtdeinit_klipper.so

This is run immediately after installation?
Try as root: ldconfig
Comment 2 Markus Raab 2014-12-25 13:05:40 CST 
Thank you for your quick resposne.

Shouldn't dpkg call ldconfig?

I have another i386 debian wheezy installation where klipper runs just fine. So severity should be reduced and you might be right. I will check on the problematic machine asap.

That apt-file does not find /opt/trinity/lib/libtdeinit_klipper.so seems to be an unrelated issue that Conents-i386.gz is missing on the server.
Comment 3 Michele Calgaro 2014-12-27 00:46:01 CST 
Most likely this is an installation/upgrade problem. Klipper working fine here as well (Jessie & Wheezy).
Comment 4 Markus Raab 2015-01-04 04:41:12 CST 
After installing other packages the problem resolved itself. klipper works now fine.

Nevertheless it seems like its a packaging problem: Packages of libraries should call ldconfig.
Comment 5 Slávek Banko 2015-01-04 04:52:31 CST 
There is one problem. Many other packages "should" call ldconfig. But if ldconfig will be call by each such package, it would cause a slowdown in installation time. Especially on less powerful computers.

So far I'm not looking, whether it is possible to schedule ldconfig as a trigger, which would be executed once at the end of the installation packages.
Comment 6 Slávek Banko 2015-07-08 12:56:31 CDT 
Fixed in commit ae112f4e (master) and a04a81b2 (r14.0.x).