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 970 - Build issue: kvpnc: unknown icon prefix
Summary: Build issue: kvpnc: unknown icon prefix
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P1 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-04-20 22:10 CDT by Darrell
Modified: 2013-12-23 15:27 CST (History)
3 users (show)

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

Attachments
Patch to fix "Unknown icon prefix" message (545 bytes, patch)
2013-12-03 00:08 CST, Darrell 		Details | Diff
Show Obsolete (1) View All 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 Darrell 2012-04-20 22:10:08 CDT 
From the configure log:

unknown icon prefix lo48 in src/icons/Makefile.in
unknown icon prefix lo64 in src/icons/Makefile.in
unknown icon prefix lo64 in src/icons/Makefile.in
Comment 1 Darrell 2013-12-03 00:08:03 CST 
Created attachment 1692 [details]
Patch to fix "Unknown icon prefix" message
Comment 2 Darrell 2013-12-18 21:33:14 CST 
This requires modifying admin/am_edit, which actually is derived from common/admin. We need to split this patch into two and then coordinate with the next patch updating of common.
Comment 3 Timothy Pearson 2013-12-18 21:41:37 CST 
Sounds like we might need an Etherpad dedicated to coordinating the common module updates.  It is also increasingly apparent that we will need one more common module update before R14 can be released.
Comment 4 Darrell 2013-12-18 21:57:02 CST 
I added a section in the R14 Road map etherpad.
Comment 5 Darrell 2013-12-23 15:23:26 CST 
This report was resolved with the recent common module patch updates from Dec.
22-23.