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 1687

Summary:	Can't load kate tabbar or katefiletemplates plugins
Product:	TDE	Reporter:	Darrell <darrella>
Component:	tdeaddons	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, darrella
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:	1655
Bug Blocks:
Attachments:	symbol list

Description Darrell 2013-10-26 12:14:29 CDT

While attempting to test the patch in bug report 1664, I noticed I cannot load the kate tabbar or katefiletemplates plugins. I select the check box in Settings but the bar never appears. When I again open Settings the check box is unchecked.

I'm using the latest git sources. Full package rebuilds each time in a clean build enviornment. Slackware 14.1 32-bit.

My xsession-errors log shows the following messages:

tdecore (KLibLoader): WARNING: KLibrary: symbol not found
tdecore (KLibLoader): WARNING: The library libkatetabbarextensionplugin does not offer an init_libkatetabbarextensionplugin function.

tdecore (KLibLoader): WARNING: KLibrary: symbol not found
tdecore (KLibLoader): WARNING: The library katefiletemplates does not offer an init_katefiletemplates function.

I am unable to get the two plugins to load. This is true for systems with or without the 1664 patch.

I have a virtual machine running Trinity git. The package set is from July 29. I observe the same behavior there in that selecting the plugin check boxes results in the tabbar not appearing and when immediately thereafter opening the Settings dialog the check boxes are cleared. I do not see the stderr messages but I suspect that is because this older package set does not include commit 5354555.

I have a 3.5.13.0 virtual machine. There I am able to enable the tabbar extension. That tells me only that something changed from 3.5.13.0 to pre R14.

The problem appears with or without the 1664 patch. I suspect tdelibs, either a corner case I have stumbled across or something in my build script configuration options.

The problem occurs with a fresh profile.

This report probably does not block R14, but blocks resolving bug report 1664.

Notice in bug report 1655 I reported the message "tdecore (KLibLoader): WARNING: KLibrary: symbol not found." In that bug report I triggered the message when using kmail. I'm guessing that tends to indicate the problem is with tdelibs.

Comment 1 Darrell 2013-10-26 13:41:36 CDT

I installed a git package set from January 2013. The problem exists then too. This problem has been around a while.

Comment 2 Darrell 2013-10-26 15:27:18 CDT

Is there a way to debug this?

Comment 3 Michele Calgaro 2013-10-27 08:25:02 CDT

Created attachment 1572 [details]
symbol list

(In reply to comment #2)
> Is there a way to debug this?

Hi Darrell,
sorry for the late reply, I haven't got much free time for TDE in the last few days. Possibly I should get some more during the week.
Go to folder /opt/trinity/lib/trinity and type:
objdump libkatetabbarextensionplugin.so -T

This will print the list of dynamic symbols. Check if you have the symbol 'init_libkatetabbarextensionplugin' in it. Probably not, judging from your xsession-errors log
I have attached the list of symbols I get running the command on my library.

If you need, I can provide also my full build logs, where you can see exactly which option is used for each file.

Comment 4 Darrell 2013-10-27 12:26:01 CDT

I ran the objdump command and as expected no such symbol appeared.

In my build script I had

--enable-gcc-hidden-visibility

On a hunch I changed that to

--disable-gcc-hidden-visibility

I rebuilt tdeaddons and then the objdump command successfully showed the desired results. I launched kate and then had no problem loading the two plugins.

I updated bug report 1285, which addresses the problem of hidden symbol visibility. I am tagging this report as resolved.