Bug 130330

Summary:	CUPS manager complains about missing symbols in cupsdconf.library
Product:	[Unmaintained] kdeprint	Reporter:	Michael Nottebrock <lofi>
Component:	general	Assignee:	KDEPrint Devel Mailinglist <kde-print-bugs-null>
Status:	CLOSED NOT A BUG
Severity:	normal	CC:	jlayt
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Michael Nottebrock 2006-07-06 01:07:51 UTC

Version:            (using KDE KDE 3.5.3)
Installed from:    FreeBSD Ports
OS:                FreeBSD

When trying to use the Print Server/Restart Server function in the KControl Printer dialog for CUPS, an error dialog is displayed:

Unable to restart print server. Error message received from manager:

Symbol restartServer not found in cupsdconf library.

This bug has been long-standing on FreeBSD, probably ever since http://websvn.kde.org/trunk/kdelibs/kdeprint/cups/kmcupsmanager.cpp?rev=281953&r1=276746&r2=281953
, but has only been recently brought to my attention again.

The symbol is indeed missing from the library:

[lofi@kiste]:0:~/kde-freebsd/area51/x11/kdelibs3/work/kdelibs-3.5.3/kdeprint > nm /usr/local/lib/kde3/cupsdconf.so
00001824 A _DYNAMIC
00001908 A _GLOBAL_OFFSET_TABLE_
         w _Jv_RegisterClasses
000018f8 d __CTOR_END__
000018f4 d __CTOR_LIST__
00001900 d __DTOR_END__
000018fc d __DTOR_LIST__
00001820 r __EH_FRAME_BEGIN__
00001820 r __FRAME_END__
00001904 d __JCR_END__
00001904 d __JCR_LIST__
00001938 A __bss_start
         w __cxa_finalize
         w __deregister_frame_info
00000740 t __do_global_ctors_aux
00000638 t __do_global_dtors_aux
00001818 d __dso_handle
         w __register_frame_info
00001938 A _edata
00001954 A _end
00000770 T _fini
000005c4 T _init
00001938 b completed.1
000006b8 t frame_dummy
0000071c T kdeinitmain
         U kdemain
0000193c b object.2
0000181c d p.0

... but is present in libkdeinit_cupsdconf.so (and replacing cupsdconf.so with a symlink to that works around the problem).

Comment 1 Kurt Pfeifle 2007-01-12 16:43:50 UTC

Michael,

is this problem still around? If so, are you able to provide a patch?

Cheers, Kurt

---------------
(Setting timeout for this bug to Feb 1, 2007)

Comment 2 Kurt Pfeifle 2007-02-03 12:25:47 UTC

closing bug due to timeout; no feedback from reporter.

Comment 3 John Layt 2008-12-31 20:12:27 UTC

Closing old Resolved status bug.