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 2168

Summary:	Amarok fails to start due to missing library
Product:	TDE	Reporter:	Kristopher <gamrat.kristopher>
Component:	tdemultimedia	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, gamrat.kristopher, michele.calgaro
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Debian Wheezy
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Kristopher 2014-10-18 20:53:02 CDT

I am using the latest R14 nightlies as of 18 October 2014 at 8:00PM (20:00 on 24-hour clocks) Eastern Time.

Attempting to start Amarok shows Amarok's splash screen for a split second, however Amarok never loads. Attempting to run Amarok from a terminal reveals the following very telling line:


/opt/trinity/bin/amarokapp: error while loading shared libraries: libknewstuff.so.1: cannot open shared object file: No such file or directory


I have the tde-core-trinity package installed, and no broken packages or missing dependencies are reported in Synaptic.

Running the command 'updatedb && locate libknewstuff.so.1" reveals that the library in question does not exist on my system, and running "ls /opt/trinity/lib/ | grep libknewstuff.so" (without the final ".1") reveals that not even another version is in existence within my TDE install (unless it was accidentally relocated to another directory?).

Comment 1 Michele Calgaro 2014-10-21 05:22:02 CDT

KNewStuff was recently converted into TDENewStuff in the GIT source. Since the status of many packages on the build farm is likely inconsisten due to the high number of changes made in recent days, you probably have an inconsistent installation.
On a consistent installation built from the last GIT sources, Amarok has no problems to run.

Please test again when you have a consistent environment (probably after RC1 is released) and let us know. If tested ok, please close the bug.

Comment 2 Michele Calgaro 2014-10-21 05:24:31 CDT

You can refer to commit b78d37d1.

Comment 3 Kristopher 2014-10-21 09:19:40 CDT

(In reply to Michele Calgaro from comment #1)
> KNewStuff was recently converted into TDENewStuff in the GIT source. Since
> the status of many packages on the build farm is likely inconsisten due to
> the high number of changes made in recent days, you probably have an
> inconsistent installation.
> On a consistent installation built from the last GIT sources, Amarok has no
> problems to run.
> 
> Please test again when you have a consistent environment (probably after RC1
> is released) and let us know. If tested ok, please close the bug.

How will I know when it's "consistent"?

Comment 4 Michele Calgaro 2014-10-21 22:05:03 CDT

When RC1 is announced (which should be reasonably soon) it should be consistent. Anyhow even before that you can try to update and see if the error has disappeared. As long as tdelibs, amarok and perhaps tdebase and tdemultimedia have been rebuilt, then Amarok should be fine.
If you still have the problem with RC1, then there is really a bug.

Comment 5 Kristopher 2014-10-22 09:37:52 CDT

My most recent update (22 October 2014 at 9:30 AM Eastern Time) included an Amarok update that fixed the issue, Amarok now runs as before. Marking as RESOLVED --> FIXED.