I just did an upgrade, and knetworkmanager seems to have suddenly
vanished from the build:
pjh@pjh-laptop:~$ sudo aptitude install knetworkmanager-trinity
"knetworkmanager-trinity" exists in the package database, but it is not a
real package and no package provides it.
--
Patricia J. Hawkins
Hi All,
Maybe somebody could give me a hint on this. I hope it's not something
obvious.
For my own benefit, I'm attempting to rebuild the Red Hat rpms targeting
armv5tel, so that I may use Trinity on my Toshiba AC100. I'm working
through the main install requirements in order to get a basic install so
I've done tqtinterface, arts, dbus-tqt, dbus-1-tqt, tdelibs along with
all the requires but can't get past tdebase.
tdebase gets almost there, but boms out at;
## ---- Start error output ---- ###
[100%] Building CXX object
kicker/kicker/CMakeFiles/kicker-module.dir/kicker_kdeinit_module.cpp.o
cd /root/rpmbuild/BUILD/kdebase/build/kicker/kicker && /usr/bin/c++
-Dkicker_module_EXPORTS -DHAVE_CONFIG_H -O2 -g -march=armv5te
-DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h
-fPIC -I/root/rpmbuild/BUILD/kdebase/libkonq -I/usr/lib/qt-3.3/include
-I/usr/include/tqt -o CMakeFiles/kicker-module
dir/kicker_kdeinit_module.cpp.-o -c
/root/rpmbuild/BUILD/kdebase/build/kicker/kicker/kicker_kdeinit_module.cpp
Linking CXX shared module kicker.so
cd /root/rpmbuild/BUILD/kdebase/build/kicker/kicker && /usr/bin/cmake -E
cmake_link_script CMakeFiles/kicker-module.dir/link.txt -verbose=1
/usr/bin/c++ -fPIC -O2 -g -march=armv5te -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -Wl,--no-undefined
-shared -Wl,-soname,kicker.so -o kicker.so
CMakeFiles/kicker-module.dir/kicker_kdeinit_module.cpp.o
-L/usr/lib/qt-3.3/lib libkdeinit_kicker.so
../libkicker/libkickermain.so.1.0.0 /usr/lib/libabc.so.1.2.0
/usr/lib/libvcard.so.0.0.0 /usr/lib/libkresources.so.1.2.0
/usr/lib/libkutils.so.1.2.0 /usr/lib/libkparts.so.2.1.0 /
sr/lib/libkio.so.4.2.0 /usr/lib/libkdeui.so.4.2.0 -lfreetype
-lfontconfig /usr/lib/libkdesu.so.4.2.0 -lutil
/usr/lib/libkwalletclient.so.1.0.1 /usr/lib/libkdecore.so.4.2.0
/usr/lib/libDCOP.so.4.2.0 /usr/lib/libkdefx.so.4.2.0 -ltqt -lqt-mt
-lXrender -lX11 -lz -lXcomposite -lXfixes -lICE -lSM
/usr/bin/ld: warning: libkonq.so.4, needed by libkdeinit_kicker.so, not
found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libkickoffsearch_interfaces.so.0, needed by
libkdeinit_kicker.so, not found (try using -rpath or -rpath-link)
libkdeinit_kicker.so: undefined reference to
`KonqBookmarkManager::s_bookmarkManager'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_invoke(int, QUObject*)'
libkdeinit_kicker.so: undefined reference to `typeinfo for
KickoffSearch::Plugin'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_property(int, int, QVariant*)'
libkdeinit_kicker.so: undefined reference to `typeinfo for
KickoffSearch::KickoffSearchInterface'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::KickoffSearchInterface(QObject*,
char const*'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::staticMetaObject()'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::Plugin::staticMetaObject()'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_cast(char const*)'
libkdeinit_kicker.so: undefined reference to `vtable for
KickoffSearch::KickoffSearchInterface'
libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_emit(int, QUObject*)'
libkdeinit_kicker.so: undefined reference to
`KonqPopupMenu::KonqPopupMenu(KBookmarkManager*, QPtrList<KFileItem>
const&, KURL const&, KActionCollection&, KNewMenu*, QWidget*, unsigned
int, unsigned int)'
libkdeinit_kicker.so: undefined reference to
`KonqOperations::doDrop(KFileItem const*, KURL const&, QDropEvent*,
QWidget*)'
collect2: ld returned 1 exit status
make[2]: *** [kicker/kicker/kicker] Error 1
make[2]: Leaving directory `/root/rpmbuild/BUILD/kdebase/build'
make[1]: *** [kicker/kicker/CMakeFiles/kicker.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/root/rpmbuild/BUILD/kdebase/build'
/usr/bin/cmake -E cmake_progress_report
/root/rpmbuild/BUILD/kdebase/build/CMakeFiles
[100%] Built target kicker-module
make[1]: Leaving directory `/root/rpmbuild/BUILD/kdebase/build'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.BTlI5u (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.BTlI5u (%build)
## ---- End error output ---- ###
Two lines from above;
/usr/bin/ld: warning: libkonq.so.4, needed by libkdeinit_kicker.so, not
found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libkickoffsearch_interfaces.so.0, needed by
libkdeinit_kicker.so, not found (try using -rpath or -rpath-link)
suggest to me it's a simple case of the libs libkonq.so.4 &
libkickoffsearch_interfaces.so.0 not being found by
libkdeinit_kicker.so. They do not exist on the system but are created
during the build process. With that in mind, I did a quick and dirty
hack of 'kicker/kicker/CMakeLists.txt' and added the two directories
containing the two 'missing' libs to the 'link_directories' stanza but
to no avail. The change adds '-L' entries for the locations of the libs
but doesn't alter the result.
Anybody know how I can rectify this correctly? I guess 'rpath' will need
to come into play also.
Any pointers appreciated.
Cheers,
Mike.
--
Any question is easy if you know the answer!
On Mon, 16 Jul 2012, Timothy Pearson wrote:
>> I just did an upgrade, and knetworkmanager seems to have suddenly
>> vanished from the build:
>
>knetwork manager is not available for distributions that use
>network-manager 0.9 or above due to the fact that critical functionality
>was removed from the upstream network-manager project.
>
>We are investigating other network management systems for inclusion in TDE
>as network-manager appears to be a poor choice for TDE at this time.
FWIW; I run wicd on a Trinity 3.5.13 NetBook.
It might help the OP move along...
BTW, Tim. Where are the attributions on your reply's quotes?
HTH
Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
Pueblo, Colorado | @ | Jonesy | OS/2 __
38.238N 104.547W | config.com | DM78rf | SK
David,
there's a tiny small bug in exegnulinux_3.3_preview4.iso :
When installing on a harddisk and activating session management ("restore
previous session") then this entry ~/.trinity/Autostart/kmix.desktop causes
kmix to start twice after the first session, which pops up the mixer dialog,
which is a bit anoying.
Otherwise, good work, I have not found an other issue :-)
Nik
--
Mag. Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
Hello,
I've finally built a LiveCD including TDE 3.5.13 (+ updates) based on
Fedora 17. The previous LiveCD was based on Fedora 16.
The CD allows to run TDE directly, but can also install Fedora on the
hard disk.
Both i686 and x86_64 versions are available.
Link:
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/rpm/f17/trinity-…
Francois
G'day List,
I'm sure that this has been asked on the list before, but my
search-foo is low and I can't find it in the list archives. So here
goes ...
Trying to setup an account in Kmail-trinity, aptitude show
kmail-trinity identifies it as
Version: 4:3.5.13-0debian9+r1258263+pr10~squeeze
if that helps. Anyway, when I get to <Configure - Kmail>, <Accounts>,
<Add> the "Add Account - Kmail" window is too big and the OK/Save box
is hidden below the bottom of the screen so nothing that I enter is
saved. Moving the panel out of the way does not help on this netbook
with 1024x600 resolution and all attempts to resize the window fail.
What is the fix/work-around, please?
Ta,
Glen (stuck in GOF mode)
I get the following error when running synaptic:
---------------------
W: GPG error: http://www.debian-multimedia.org wheezy Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 07DC563D1F41B907
W: GPG error: http://ppa.quickbuild.pearsoncomputing.net squeeze Release: The
following signatures were invalid: BADSIG 43F1DC4F2B8638D0 QuickBuild Trinity
Desktop Environment
----------------------
what's the best way of fixing it?
cheers
ant
--
Sent from my linux system running Debian 6, desktop trinity-KDE.
This email is plain text, not HTML. Any attachments are either .jpeg or .pdf
> On 9 July 2012 14:18, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
>
>> We are pleased to announce the addition of a full suite of
LDAP/Kerberos tools to the TDE bounty program! These tools are geared
towards enterprise users, and cover all aspects of creating, managing,
and using LDAP/Kerberos realms. For more information, screenshots,
statistics, and
>> demo videos, please visit the TDE RFE page at
>> http://www.trinitydesktop.org/crfe/#finished
>>
>> Timothy Pearson
>> Trinity Desktop Project
>>
>
> Seems really cool a few questions,
>
> "You would NOT receive a refund in this case, so you may wish to handle
pledges and funds collection/delivery in collaboration with your
business, local Linux user's group, or similar third party."
>
> What is the reason for this?
Basically I don't want to be an escrow service. ;-) I don't know what the
legal ramifications would be were I to provide such services. I prefer
that interested parties group together to collect the funds on their own,
then post the bounty in one large chunk.
> What happens if we only get as far as getting the library released? Will it
> all be for naught?
Well, it depends. :-) The library is actually quite powerful in and of
itself, but obviously there is no GUI associated with it.
> Is it worth contacting a larger group using KDE3/Trinity software (any
corporation, maybe even the group from munich may be interested?
Yes! If you know of potentially interested parties please send them a
link to the provided information.
If you have any further questions, including detailed questions about the
software, don't hesitate to ask!
Tim
We are pleased to announce the addition of a full suite of LDAP/Kerberos
tools to the TDE bounty program! These tools are geared towards
enterprise users, and cover all aspects of creating, managing, and using
LDAP/Kerberos realms. For more information, screenshots, statistics, and
demo videos, please visit the TDE RFE page at
http://www.trinitydesktop.org/crfe/#finished
Timothy Pearson
Trinity Desktop Project