I have released porteus-v1.2rc1 so should start getting some reports from
users in everyday life now. One thing i noticed with the pretty stuff was
that the ksplash-engine-moodin was that it shows up in the kcontrol, but an
error message 'This theme requires the plugin Moodin' is received and the
splash will not preview. Others give the message that the plugin: default
is required. This is also true for the 'fingerprint' splash by Tim.
twin-crystal-theme just doesn't show up in the themes at all.
Can someone please confirm this from a running Trinity desktop. If it is
just me then i will start digging.
Jay
When starting X/TDE from a login manager, the Shutdown confirmation dialog displays a Restart button with a little arrow.
Selecting and holding the button reveals the options to select how the system restarts. The button options are from the GRUB menu.lst.
I don't know whether LILO options are supported.
How is the default GRUB boot option supposed to get changed? That is, the user needs admin permissions to modify menu.lst.
When the user does not have those permissions, should the Restart button then be a generic button with no options like the other buttons?
Darrell
This past summer several apps were modified and the commit message says "This enables compilation under both Qt3 and Qt4."
What does that mean?
Does that mean the app's older Qt3 code is still used but modified to allow building against Qt4? Or does that mean the newer Qt4 version has been modified to build with TQt3?
Darrell
All,
Is there any reason not to use libjpeg-turbo instead of libjpeg when
building tde? Why not benefit from the acceleration?
--
David C. Rankin, J.D.,P.E.
All,
Can someone who has kdm built from the latest git run ldd against it to see
if it still needs libshadow. (I'm sure there is a way to check the source, but
I don't know it yet :) With shadow >= 4.1.5, libshadow is no longer provided
on Arch (or any distro I suspect). Just a quick:
ldd /opt/tde/bin/kdm
will do it...
--
David C. Rankin, J.D.,P.E.
I see these warnings when building Trinity packages. They are non destructive warnings, the packages still build. I'm not a C++ guru but a quick browsing around the web indicates that this warning probably indicates sloppy code. Some examples:
tdegraphics/kooka/thumbview.h:57: warning: declaration 'class KIO::PreviewJob' does not declare anything
tdenetwork/kopete/libkopete/ui/metacontactselectorwidget.h:26: warning: declaration 'class Kopete::MetaContact' does not declare anything
amarok/amarok/src/metadata/rmff/rmff.h:281: warning: declaration 'class TagLib::AudioProperties' does not declare anything
Quality and robustness are always high on my priorities with Trinity. Should we address these warnings? If yes, then how can C++ newbies like me help with patching? That is, what is the appropriate fix for those warnings?
Darrell