>This topic deserves further investigation.
Some quick testing reveals the problem experienced by the blog
author is the XDG environment variables.
That said, here is a list of Trinity *.desktop files using
OnlyShowIn=TDE
==========================================================
applications/adept/adept/notifier/adept_notifier_auto.desktop
applications/desktop-effects-tde/desktop-effects-tde.desktop
applications/gtk-qt-engine/kcm_gtk/kcmgtk.desktop
applications/knutclient/src/knutclient.desktop
applications/krusader/krusader/krusader_root-mode.desktop
applications/tde-guidance/powermanager/guidance-power-
manager.desktop
libraries/pytdeextensions/pytdeextensions.desktop
tdebase/kappfinder/kappfinder.desktop
tdebase/kcontrol/kcontrol/KControl.desktop
tdebase/kcontrol/randr/tderandrtray.desktop
tdebase/kdesktop/init/Home.desktop
tdebase/kdesktop/init/System.desktop
tdebase/kfind/Kfind.desktop
tdebase/khelpcenter/Help.desktop
tdebase/kicker/kicker/kcmkicker.desktop
tdebase/kicker/kicker/panel.desktop
tdebase/klipper/klipper.desktop
tdebase/kmenuedit/kmenuedit.desktop
tdebase/konqueror/Home.desktop
tdebase/konqueror/preloader/konqy_preload.desktop
tdebase/kpersonalizer/kpersonalizer.desktop
tdebase/ktip/ktip.desktop
tdebase/tdescreensaver/KBlankscreen.desktop
tdebase/tdescreensaver/KRandom.desktop
tdelibs/tdeabc/tdeab2tdeabc.desktop
tdelibs/tderesources/tderesources.desktop
tdemultimedia/arts/builder/artsbuilder.desktop
tdemultimedia/arts/builder/x-artsbuilder.desktop
tdemultimedia/arts/tools/artscontrol.desktop
tdemultimedia/arts/tools/artscontrolapplet.desktop
tdemultimedia/kmix/kmix.desktop
tdemultimedia/kmix/restore_kmix_volumes.desktop
tdenetwork/filesharing/advanced/kcm_sambaconf/kcmsambaconf.desktop
tdepim/kalarm/kalarm.desktop
tdepim/korganizer/korgac/korgac.desktop
tdepim/tdeabc/tdeabcdistlistupdater/tdeabcdistlistupdater.desktop
tdeutils/kdf/kwikdisk.desktop
tdeutils/superkaramba/src/superkaramba.desktop
==========================================================
From this list, I think only the following are candidates for
change:
tdepim/kalarm/kalarm.desktop -> NotShowIn=KDE
tdepim/korganizer/korgac/korgac.desktop -> NotShowIn=KDE
tdeutils/kdf/kwikdisk.desktop -> NotShowIn=KDE
Of the remaining Trinity *.desktop files, the question remains
whether any TDE app that has the same name as in KDE4 should use
NotShowIn=KDE. Such a change would be noticeable only when a user
or admin modifies the XDG_* environment variables to search
/opt/trinity. When KDE4 and Trinity are installed concurrently, any
such change would remove the Trinity version from the menu and
leave only the KDE4 version.
I think a better strategy is find a way to improve the menus of
other environments.
There are two anomalies:
NotShowIn=GNOME:
tdebase/konqueror/konquerorsu.desktop
tdebase/ksysguard/gui/x-ksysguard.desktop
Darrell
> There are a number of png files in TDE that generate errors on
>opening due to
>outdated png header information. I would like to identify which
>icons these are.
>For example when opening khelpcenter I receive the following
>messages:
>
>03:03 valhalla:~> khelpcenter help:/khelpcenter/releasenotes
>khelpcenter: WARNING: Main template file name is empty.
>libpng warning: iCCP: known incorrect sRGB profile
>libpng error: IDAT: invalid distance too far back
>libpng error: IDAT: invalid distance too far back
>libpng error: IDAT: invalid distance too far back
>libpng warning: Interlace handling should be turned on when using
>png_read_image
>libpng error: IDAT: invalid distance too far back
>libpng error: IDAT: invalid distance too far back
>libpng error: IDAT: invalid distance too far back
>libpng warning: Interlace handling should be turned on when using
>png_read_image
>
> Apparently, the problem is out-of-date png header information.
>Searching I
>stumbled across a minimal bit of source that is supposed to fix
>the issue, but
>only if compiled on older versions of libpng. Looking at the code,
>the crux of
>it is to rewrite the first 8 bytes of the png header. I've
>attached it for
>experimentation. It builds well on all of the boxes I have, but I
>suspect you
>have to force it to build against libpng 1.2 in order for it to do
>what it is
>supposed to. I'll continue to experiment. If you have few spare
>minutes give it
>a try and let me know if you can see any discernible difference in
>the new/old
>png files. I haven't yet.
This is a bug report against newer versions of libpng. I don't seen
any such errors with libpng 1.4.12.
I suspect a rite of initiation to become a libpng developer is to
introduce new code that breaks something for everybody downstream.
Cousins to the BOFH.
Darrell
>Well, I did a cursory test ages ago just to get a handle on what
>had
>CMakeLists.txt and what didn't. If we could identify solid
>criteria like you
>suggested "directories with both CMakeLists and Makefile.am"
>files, then it
>would be a simple process of walking the git tree with 'find' and
>identifying
>apps which met the checks and those that partially met and those
>that were just
>autofoo.
>
>One issue I see is the use of .in.in and .in instead of .am, so we
>may need a
>fairly broad search of the variants of Makefile.am, configure.blah
>to get a
>valid picture of the state of the build setup.
>
>I'll look for some tests, if you can think of others, let us know.
>
>Everybody else as well.
Here is a preliminary list of modules converted to cmake that
contain directories with a Makefile.am but no corresponding
CMakeLists.txt. The list offers no conclusions. Just a list. Which
items are legitimate remains to be investigated.
amarok/amarok/src/engine/helix
amarok/amarok/src/engine/helix/config
amarok/amarok/src/engine/helix/helix-sp
amarok/amarok/src/engine/kdemm
amarok/amarok/src/engine/mas
amarok/amarok/src/engine/nmm
amarok/amarok/src/engine/nmm/icons
amarok/amarok/src/metadata/speex
amarok/amarok/src/metadata/trueaudio
amarok/amarok/src/metadata/wavpack
amarok/amarok/src/scripts/graphequalizer
amarok/amarok/src/sqlite
dolphin/doc
dolphin/doc/en
dolphin/po
knetworkmanager8/knetworkmanager-0.8/introspection
knetworkmanager8/knetworkmanager-0.8/po
knetworkmanager8/knetworkmanager-0.8/vpn-plugins
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/openvpn
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/openvpn/src
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/pptp
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/pptp/src
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/strongswan
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/strongswan/src
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/vpnc
knetworkmanager8/knetworkmanager-0.8/vpn-plugins/vpnc/src
tdebase/doc/kappfinder
tdebase/kcontrol/accessibility
tdebase/kcontrol/smartcard
tdebase/khelpcenter/htmlsearch
tdebase/kicker/applets/swallow
tdebase/kicker/kicker/plugins
tdebase/kicker/menuext/tom
tdebase/konqueror/sidebar/test
tdebase/konsole/doc
tdebase/konsole/doc/VT100
tdebase/ksysguard/ksysguardd/FreeBSD
tdebase/ksysguard/ksysguardd/Irix
tdebase/ksysguard/ksysguardd/NetBSD
tdebase/ksysguard/ksysguardd/OpenBSD
tdebase/ksysguard/ksysguardd/Solaris
tdebase/ksysguard/ksysguardd/Tru64
tdebase/libkonq/tests
tdebase/nsplugins/test
tdebase/nsplugins/wrapper
tdebase/tdeprint/descriptions
tdebase/twin/clients/kwmtheme
tdebase/twin/clients/kwmtheme/cli_installer
tdebase/twin/clients/test
tdebase/twin/tools
tdebase/twin/tools/decobenchmark
tdegraphics/ksvg/plugin/backends/agg
tdegraphics/kview/kviewcanvas/test
tdegraphics/kview/kviewviewer/test
tdegraphics/kview/modules/scale
tdegraphics/kview/modules/template
tdelibs/arts/kde/mcop-dcop
tdelibs/dcop/tests
tdelibs/doc/tdelibs
tdelibs/interfaces/terminal/test
tdelibs/kate/plugins/autobookmarker
tdelibs/kded/test
tdelibs/libtdemid/tests
tdelibs/tdeabc/plugins/evolution
tdelibs/tdeabc/plugins/sql
tdelibs/tdeabc/scripts
tdelibs/tdeabc/tests
tdelibs/tdecore/tdeconfig_compiler/example
tdelibs/tdecore/tdeconfig_compiler/tests
tdelibs/tdecore/tests
tdelibs/tdehtml/java/tests
tdelibs/tdeinit/tests
tdelibs/tdeio/tdefile/tests
tdelibs/tdeioslave/http/kcookiejar/tests
tdelibs/tdemdi/test
tdelibs/tdeparts/tests
tdelibs/tdeprint/foomatic
tdelibs/tdeprint/lpd
tdelibs/tdeprint/tests
tdelibs/tdespell2/tests
tdelibs/tdestyles/klegacy
tdelibs/tdestyles/web
tdelibs/tdeui/colors
tdelibs/tdeutils/tests
tdelibs/tdewallet/backend/tests
tdelibs/tdewallet/tests
tdelibs/tdewidgets/tests
tdenetwork/kopete/kopete/chatwindow/tests
tdenetwork/kopete/libkopete/compat
tdenetwork/kopete/libkopete/tests
tdenetwork/kopete/libkopete/tests/mock
tdenetwork/kopete/plugins/smpppdcs/unittest
tdenetwork/kopete/protocols/groupwise/libgroupwise/tasks/tests
tdenetwork/kopete/protocols/groupwise/libgroupwise/tests
tdenetwork/kopete/protocols/jabber/jingle/libjingle/talk/examples
tdenetwork/kopete/protocols/jabber/jingle/libjingle/talk/examples/ca
ll
tdenetwork/kopete/protocols/jabber/jingle/libjingle/talk/examples/lo
gin
tdenetwork/kopete/protocols/oscar/liboscar/tests
tdenetwork/kopete/protocols/yahoo/libkyahoo/tests
tdenetwork/ksirc/puke
tdepim/certmanager/lib/backends/kpgp
tdepim/certmanager/lib/tests
tdepim/indexlib/tests
tdepim/karm/test
tdepim/kitchensync/opensyncdbus
tdepim/kmail/tests
tdepim/kmobile/tdeioslave
tdepim/kmobile/tdeioslave/mimetypes
tdepim/kode/kwsdl
tdepim/kode/kwsdl/kung
tdepim/kode/kwsdl/schema
tdepim/kode/kwsdl/tests
tdepim/kode/kwsdl/tests/google
tdepim/kode/kwsdl/wscl
tdepim/kontact/plugins/kitchensync
tdepim/kontact/plugins/kpilot
tdepim/kontact/plugins/test
tdepim/korganizer/plugins/printing/list
tdepim/korganizer/plugins/printing/whatsnext
tdepim/korganizer/plugins/projectview
tdepim/korganizer/plugins/timespanview
tdepim/ktnef/tests
tdepim/libemailfunctions/tests
tdepim/libkcal/tests
tdepim/libkmime/tests
tdepim/libksieve/tests
tdepim/libtdenetwork/libgpg-error-copy
tdepim/libtdenetwork/libgpgme-copy
tdepim/libtdenetwork/libgpgme-copy/assuan
tdepim/libtdenetwork/libgpgme-copy/gpgme
tdepim/libtdenetwork/qgpgme/tests
tdepim/libtdepim/cfgc
tdepim/libtdepim/interfaces
tdepim/libtdepim/komposer
tdepim/libtdepim/komposer/core
tdepim/libtdepim/komposer/core/tests
tdepim/libtdepim/komposer/plugins
tdepim/libtdepim/komposer/plugins/default
tdepim/libtdepim/komposer/test
tdepim/libtdepim/tests
tdepim/tdeabc/frontend
tdepim/tdefile-plugins/palm-databases
tdepim/tdefile-plugins/rfc822
tdepim/tdeioslave/opengroupware
tdepim/tderesources/blogging
tdepim/tderesources/groupware
tdepim/tderesources/tvanytime
tdesdk/doc/kapptemplate
tdesdk/kbabel/kbabeldict/modules/dbsearchengine2
tdesdk/poxml/antlr/antlr
tdesdk/tdeunittest/example
tdesdk/tdeunittest/example/module
tdesdk/tdeunittest/example/simple
tdesdk/umbrello/umbrello/autolayout
tdevelop/buildtools/lib/parsers/autotools/tests
tdevelop/buildtools/lib/parsers/qmake/tests
tdevelop/doc/kdearch
tdevelop/doc/tools
tdevelop/kdevdesigner/plugins
tdevelop/languages/cpp/app_templates/generichello
tdevelop/languages/cpp/app_templates/gnome2mmapp
tdevelop/languages/cpp/app_templates/kmake
tdevelop/languages/cpp/app_templates/prc-tool
tdevelop/languages/java/newclass_templates
tdevelop/languages/kjssupport
tdevelop/languages/kjssupport/subclassing_template
tdevelop/languages/kjssupport/template
tdevelop/parts/documentation/plugins/djvu
tdevelop/parts/documentation/plugins/pdb
tdevelop/parts/documentation/plugins/pdf
Darrell
>Perhaps it is worth do a complete check of what is completed and
>what not. That means check every single package.
I agree. How?
For example, dolphin was listed in the etherpad as completed. Yet I
compiled dolphin with cmake and no doc or po files were compiled.
Therefore I deleted the 'completed' tag in the etherpad and wrote a
note.
I know that not all components of amarok were converted and I filed
a bug report against that a very long time ago.
As I mentioned, the cmake packages do not build man pages. Another
bug report filed.
This is part of why I am suspicious of whether all packages have
been converted completely.
To my knowledge we no longer can build the core packages with
automake. Only cmake. Therefore the only file-by-file comparison we
can attempt is with a fully compiled 3.5.13.2 package. We have to
account for the renaming changes. Yet everybody builds packages
differently. Using a 3.5.13.2 package as a baseline does not mean
all components were compiled.
Darrell
Hi all!
Could sombody please send me a build script for debian?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
> For renamed files, get rid of 'NotShowIn='. If NotShowIn=KDE is
>all that is
>needed to prevent the TDE/KDE conflict for those apps that have
>NOT been
>renamed, the warm up 'sed' and make the change. If I recall
>correctly, the only
>downside to eliminating NotShowIn= completely for every desktop
>file is that you
>would get both versions of of KDE3 and KDE4 application in the
>menu. SuSE
>initially changed the title in the KDE4 apps to include KDE4-blah
>which provided
>separation in the menus but the menus did look a bit cluttered
>with double-apps
>everywhere.
>
> Since we have been on this huge renaming kick to prevent
>conflict, then I say
>get rid of 'NotShowIn=' in every application that has been
>renamed. Yes kde4
>with see tde apps, but that is an upgrade, not a problem.
>
> Turn the issue around, does any other desktop include
>'NotShowIn=TDE' to
>prevent TDE from seeing all their apps - no. I don't think we need
>any of these
>training-wheels except in case of direct TDE/KDE name conflict.
I tested this in fluxbox and xfce. I see no Trinity apps in the
menus.
Upon further reflection, although possibly we have been overzealous
with using OnlyShowIn=TDE, I suspect not. We do need to use that
directive for certain apps, but I don't think that is the root
cause of the problem described by the blog author.
I suspect the problem with other environments not seeing Trinity
apps is environment variables. As just about all of us build
Trinity to install to /opt/trinity, not a single environment
default configuration will find Trinity apps with standard
environment variables. Specifically the XDG_* variables that affect
finding trinity files.
I believe then the first hurdle is how to help other environments
find all Trinity *.desktop files.
I wonder whether we should install the menu files to /etc/xdg/menus
rather than /etc/trinity/xdg/menus.
A caveat: when KDE4 is concurrently installed with Trinity, the
respective environment menu can become a hopeless cluttered mess.
This is true in my xfce test. We have a build-time option to add
"[KDE4]" to all KDE menu items, but that might affect only the
Trinity menus. I'd have to run a build test to see any effects on
the Xfce menu.
This topic deserves further investigation.
Darrell
>I'll give it a try. But I learned during the original problem I
>had with sound,
>root uses a completely different sound scheme than normal users in
>TDE. root
>makes use of alsa-raw which bypasses a bulk of the user sound
>config, so it may
>work fine and still not be a permission issue.
If true then file a bug report. There should be no reason why root
should use arts differently than non-root users.
>Since this is virtualbox, I'll just create users doug, sally, ben
>and jerry and have totally different profiles :)
At this point I say stop and test with real hardware. Virtual
machines work great for many things, but your particular problem
needs to be resolved with real hardware. Get a second machine,
create a second partition. I use all of the above for testing.
Darrell
Recently Trinity was given a nominal public review in a blog:
http://anarchic-order.blogspot.com/2014/02/installing-trinity-
desktop-environment.html
The author offered a caveat:
"The Trinity-DE applications are only available through the Trinity-
DE desktop. While all the other applications installed on your
system show up in the TDE menus, because of the way Trinity-DE
loads its menus, if you log in with Xfce, the Trinity-DE
applications will not be seen."
Most Trinity *.desktop files use OnlyShowIn=TDE, which causes the
author's observations.
Should users of other environments (many window managers support a
menu system too) be prevented from using Trinity apps? Probably
not. The original motivation for using OnlyShowIn=TDE is conflicts
and confusion in the Trinity and KDE menus because many apps share
the same name. Perhaps NotShowIn=KDE is more apprpriate than
OnlyShowIn=TDE?
I believe we should resolve this before releasing R14.
Comments?
Darrell
All,
There are a number of png files in TDE that generate errors on opening due to
outdated png header information. I would like to identify which icons these are.
For example when opening khelpcenter I receive the following messages:
03:03 valhalla:~> khelpcenter help:/khelpcenter/releasenotes
khelpcenter: WARNING: Main template file name is empty.
libpng warning: iCCP: known incorrect sRGB profile
libpng error: IDAT: invalid distance too far back
libpng error: IDAT: invalid distance too far back
libpng error: IDAT: invalid distance too far back
libpng warning: Interlace handling should be turned on when using png_read_image
libpng error: IDAT: invalid distance too far back
libpng error: IDAT: invalid distance too far back
libpng error: IDAT: invalid distance too far back
libpng warning: Interlace handling should be turned on when using png_read_image
Apparently, the problem is out-of-date png header information. Searching I
stumbled across a minimal bit of source that is supposed to fix the issue, but
only if compiled on older versions of libpng. Looking at the code, the crux of
it is to rewrite the first 8 bytes of the png header. I've attached it for
experimentation. It builds well on all of the boxes I have, but I suspect you
have to force it to build against libpng 1.2 in order for it to do what it is
supposed to. I'll continue to experiment. If you have few spare minutes give it
a try and let me know if you can see any discernible difference in the new/old
png files. I haven't yet.
--
David C. Rankin, J.D.,P.E.