All,
I have noticed that when looking at kcontrol Appearance/Themes Screensaver,
the dialog begins to open, then kcontrol crashes. This happens every time. On an
odd instance, all of the screensavers will appear, but now it craters 100% of
the time.
I have looked at the xsession-errors log and it indicates the following:
[tdeinit] Got EXT_EXEC 'tdecmshell' from launcher.
libpng error: IDAT: invalid distance too far back
OpenGL Error: DLL Loader couldn't find/open VBoxOGLpackspu.so
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x3800006
Apparently, the file that cannot be located is hidden in plain sight:
14:22 valhalla:~> find /usr/lib -name VBoxOGLpackspu.so
/usr/lib/VBoxOGLpackspu.so
I can confirm that the crash corresponds to the 'OpenGL Error: DLL Loader
couldn't find/open VBoxOGLpackspu.so' message, but why is it not finding the
file it is looking for at /usr/lib/VBoxOGLpackspu.so?
--
David C. Rankin, J.D.,P.E.
All,
Since sound is now working on my install, I was setting sound system
notifications for events I like feedback on, i.e. shade/unshade,
maximize/minimize/restore, etc.. After clicking the '[ ] play sound' for the
event and confirming the sound file was present and working by pressing the '|>'
button before the sound filename, and then clicking [Apply] I was surprised to
find that TDE did not play anything on the events I configured.
Playing the sound file with the test '|>' button worked find, but TDE was not
responding to the sound events I chose at all. What to check?
Also, artsd has gone back to eating 10-17% of the CPU for the 60 second
'autosusped if idle for' period after a sound event. After the 60 second
autosuspend period, artsd quiets back down. Why are we setting a 60 second
autosuspend by default? Why not set it to 1 or 5 seconds. It would sure make TDE
run better giving users back 10-20% of their CPU for the remaining 55 seconds of
the timeout. Further, if the user has sound events enabled for a bulk of the
events as many sound themes do for TDE, then with an autosuspend set at 60,
artsd will be basically grinding away full time.
Can we set that to 5 sec by default instead of 60? What are the pros/cons of
shortening the autosuspend period? I've seen some of the sound server pages
(pulse - perfect setup page) recommending 1 second for the setting. Thoughts?
--
David C. Rankin, J.D.,P.E.
Hi all, Darrell,
it appears that it is necessary to add to CMake rule to find path to htsearch.
The default path is /usr/lib/cgi-bin/htsearch. Commit 83f044c5 changed the
path to /srv/www/cgi-bin/htsearch - probably specific to certain
distributions. However at least on Debian and Ubuntu it caused a problem.
Therefore, I propose add to CMake rule to search cgi-bin/htsearch on usual
paths (/usr/lib, /srv/www, some other?). With the fact that is possible to
set the path as a build option.
What do you think?
--
Slavek
>Are there any other not complete CMakeLists.txt traps waiting?
Look in my build scripts, near the top of each, for whether I have
the AUTOTOOLS variable enabled:
applications/amarok/amarok.SlackBuild -> I use autotools
applications/dolphin/dolphin.SlackBuild -> I use autotools
applications/konversation/konversation.SlackBuild
applications/kpilot/kpilot.SlackBuild -> I use autotools
applications/tde-systemsettings/tde-systemsettings.SlackBuild -> I
use autotools
tde-i18n/tde-i18n.SlackBuild
tdeaddons/tdeaddons.SlackBuild
tdemultimedia/tdemultimedia.SlackBuild -> I use autotools
tdenetwork/tdenetwork.SlackBuild
tdesdk/tdesdk.SlackBuild
tdetoys/tdetoys.SlackBuild
tdeutils/tdeutils.SlackBuild
tdewebdev/tdewebdev.SlackBuild -> I use autotools
>Here is what I am building with cmake:
Side note:
>tde-knetworkmanager9 -> this is for HAL systems, otherwise use
tdenetworkmanager
>tde-kpowersave-> ditto, use tdepowersave
Darrell
>Where can I get a copy of your updates? I've read through the
>bug, but haven't
>a clue how that translates into what it means to my build scripts.
http://humanreadable.nfshost.com/misc/tde-buildtree.tar.gz
The required changes are in the configuration and paths. Just diff
those sections to your build scripts and you'll see.
Darrell
>(1) There is no documentation available for /quanta/index.html
I have a handbook on my system.
Are you building tdewebdev with cmake or automake? cmake conversion
never was completed. If you look at the top level CMakeLists.txt in
tdewebdev you'll notice there is no configuration instruction to
build docs and in the doc directory there is no CMakeLists.txt.
IOW, no docs will be built if you use cmake.
>(2) below:
>
>01:37 valhalla:~> cat $TDEHOME/share/apps/quanta/plugins.rc
>cat: /home/david/.trinity/share/apps/quanta/plugins.rc: No such
>file or directory
Interesting. I wonder then what caused the dialog to appear, but if
you are building with cmake then that might be the cause. As the
cmake conversion is incomplete then other things might break too.
>01:48 valhalla:~> cat $TDEDIR/share/apps/quanta/plugins.rc
>[General]
>Plugins=KFileReplace, CVS Management (Cervisia),XSLT Debugger,
>KImageMapEditor,
>Link Checker, Konsole
>SearchPaths=
>
>[CVS Management (Cervisia)]
>Arguments=
>FileName=trinity/libcervisiapart.la
>Icon=cervisia
>Location=
>OutputWindow=Editor View
>Standard=true
>Standard Name=cervisia_kpart
>Type=KPart
>Input=3
>
>[KFileReplace]
>Arguments=
>FileName=trinity/libtdefilereplacepart.la
>Icon=tdefilereplace
>Input=3
>Location=
>OutputWindow=Editor Tab
>ReadOnly=true
>Standard=false
>Type=KPart
>
>[XSLT Debugger]
>Arguments=
>FileName=trinity/libkxsldbgpart.la
>Icon=xsltproc.png
>Input=0
>Location=
>OutputWindow=Editor Tab
>ReadOnly=true
>Standard=false
>Type=KPart
>
>[KImageMapEditor]
>FileName=trinity/libkimagemapeditor.la
>Icon=kimagemapeditor
>Input=1
>Location=
>OutputWindow=Editor Tab
>ReadOnly=true
>Standard=false
>Type=KPart
>
>[Link Checker]
>FileName=trinity/libklinkstatuspart.la
>Icon=klinkstatus
>Input=1
>Location=
>OutputWindow=Editor Tab
>ReadOnly=true
>Standard=false
>Type=KPart
>
>[Konsole]
>FileName=trinity/libkonsolepart.la
>Icon=konsole
>Input=1
>Location=
>OutputWindow=Separate Toolview
>ReadOnly=true
>Standard=false
>Type=KPart
>
> I don't know why I don't have a local copy. Perhaps none needed?
To my knowledge, a user copy is not necessary or created when the
environment matches the global plugins.rc file.
Darrell
> Running Quanta+ in R14 results in a dialog appearing noting that
>various
>helper applications that quata uses cannot be found:
>
>Some applications required for full functionality are missing or
>installed
>incorrectly:
>
>- Kommander [various script based dialogs including the Quick
>Start dialog] will
>not be available;
>- Tidy [HTML syntax checking] will not be available;
>- KXSLDbg [XSLT debugging] will not be available;
>- KImageMapEditor [editing HTML image maps] will not be available;
>- KLinkStatus [link validity checking] will not be available.
>
> I don't know if these are pieces of tdelibs, tdebase or some
>external
>application that quanta isn't seeing and finding, but I've built
>all the develop
>applications and applications in the git tree that were not
>bibletime related,
>etc.., so this may be a side-effect of K->T renaming.
Yes, related to renaming.
Please paste a copy of your $TDEHOME/share/apps/quanta/plugins.rc.
I need to see the exact way the information is stored in plugins.rc
with respect to the apps you cited above. Patching r14-xdg-update
will be straightforward as we already have a section for
plugins.rc. Looks like you uncovered more. :)
Tidy I'm not sure, as that is not a Trinity package. You might need
to install Tidy from upstream, but let's see what plugins.rc shows.
Darrell
>Does anybody have the help handbook index working?
>
>After building the index, I ran a search for the term cgi. The
>result is a white page:
>
>Search Results for 'cgi':
>
>Top-Level Documentation
>
>Application Manuals
>
>khc_htsearch.pl --docbook --
>indexdir=/root/.trinity/share/apps/khelpcenter/index/ --
>config=tde_application_manuals --words=cgi --method=and --maxnum=5
>-
>-lang=en
Problem found. The path location in khc_htsearch.pl was old and
needed updating. I pushed a patch.
Darrell
All,
Does anybody have the help handbook index working?
After building the index, I ran a search for the term cgi. The
result is a white page:
Search Results for 'cgi':
Top-Level Documentation
Application Manuals
khc_htsearch.pl --docbook --
indexdir=/root/.trinity/share/apps/khelpcenter/index/ --
config=tde_application_manuals --words=cgi --method=and --maxnum=5 -
-lang=en
Same type of results for other terms.
Darrell