Bugzilla Bug 121678

Starting k3d returns this error:

ERROR: Shader source path [/usr/share/k3d/shaders/layered] does not exist. 
Shutting down.

Note that the ebuild does have the code to create this directory but it doesn't
seem to be working:

        #missing dir
        dodir /usr/share/k3d/shaders/layered

Adding this directory gets past this problem but doesn't launch. I get the
following error:

/usr/bin/k3d-bin: symbol lookup error: /usr/bin/k3d-bin: undefined symbol:
_ZN3k3d26application_implementationC1ERNS_26iplugin_factory_collectionERNS_18ishader_collectionERNS_12irender_farmERNS_15iuser_interfaceERKN5boost10filesystem4pathESD_

Don't know if it is related to the layered directory or if it is another issue.

--Dan

Does 0.5.0.34 work ok for you?

(In reply to comment #1)
> Does 0.5.0.34 work ok for you?
> 

0.5.0.34 does create the layered directory properly which is the subject of
this bug. However, it still doesn't work for me:

WARNING: Resetting options data to version 2
/usr/bin/k3d-bin: symbol lookup error: /usr/bin/k3d-bin: undefined symbol:
_ZN3k3d25plugin_factory_collection14message_signalEv

A "heads up" that K-3D CVS no longer searches for specific shader directories
at startup, so this bug will become obsolete (and the ebuild can be made
simpler).

The undefined symbol is referring to a symbol that hasn't existed since K-3D
0.5.0.35, are you sure you don't have some old binaries hanging around?

Cheers,
Tim

Hi Tim,

(In reply to comment #3)
> A "heads up" that K-3D CVS no longer searches for specific shader directories
> at startup, so this bug will become obsolete (and the ebuild can be made
> simpler).

I have K-3D installed in /opt and it seems to be building and working fine but
I wanted to see how the ebuild in portage was working since I have had problems
with it in the past.

> The undefined symbol is referring to a symbol that hasn't existed since K-3D
> 0.5.0.35, are you sure you don't have some old binaries hanging around?

Is your comment referring to my original post or the more recent Comment #2?
The undefined symbol in k3d-0.5.0.37 was:
_ZN3k3d26application_implementationC1ERNS_26iplugin_factory_collectionERNS_18ishader_collectionERNS_12irender_farmERNS_15iuser_interfaceERKN5boost10filesystem4pathESD_

The undefined symbol in k3d-0.5.34 was:
_ZN3k3d25plugin_factory_collection14message_signalEv

Both were installed via the ebuilds in portage so the old binaries should have
been cleaned up. I just 'emerge unmerged k3d' and all the binaries and shared
directories seemed to have been removed.

Anyway, looking for the next version which should hopefully take care of this
bug.

--Dan

My ability to help fix this is limited (undefined symbol wise), since compiling
k3d takes a very very long time in my box each time.

Here is what I did:
I added a 0.4.5.0 ebuild, based on a 0.4.4.2 ebuild that I removed from the
tree not so long ago. It is considered the most recent "stable" version in the
project's sourceforge page.

In 0.5.0.37-r1, I dropped qt and javascript USE flags and their functions as
recommended by upstream (Tim) in bug 121869. I also added a keepdir
/usr/share/k3d/shaders/layered, while it is necessary, so that it does not get
automatically removed by Portage.

Closing a stale bug, if you have issues w/ 0.6.7.0 then file a new one. Thanks.