>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
Darrell, All,
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.
--
David C. Rankin, J.D.,P.E.
> I think my sound not working is a hal/nohal issue. I just opened
>a 3.5.13-sru
>install with the in the exact same virtualbox environment and
>sound works
>beautifully. The only difference is that install loads hal and R14
>doesn't. Have
>there been other sound problem with the nohal builds? I've
>attached my
>perirpherals-hardware-sound setup for review. It is the exact same
>between
>3.5.13-sru and R14.
Start at the beginning. Find a wave file and test that the aplay
command produces output. If not then run alsamixer.
Darrell
>On R14 I have the following sound packages installed:
>
>libpulse 4.0-6
>pulseaudio 4.0-6
>pulseaudio-alsa 2-2
>
>$ aplay /opt/trinity/share/sounds/KDE_Window_UnSticky.wav
>
>ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
>ALSA lib conf.c:4248:(_snd_config_evaluate) function
>snd_func_card_driver
>returned error: No such file or directory
>ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
>ALSA lib conf.c:4248:(_snd_config_evaluate) function
>snd_func_concat returned
>error: No such file or directory
>ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
>ALSA lib conf.c:4248:(_snd_config_evaluate) function
>snd_func_refer returned
>error: No such file or directory
>ALSA lib conf.c:4727:(snd_config_expand) Evaluate error: No such
>file or directory
>ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM sysdefault
>aplay: main:722: audio open error: No such file or directory
>
>$ aplay -l
>
>aplay: device_list:268: no soundcards found...
>
>$ aplay -L
>
>null
> Discard all samples (playback) or generate zero samples
>(capture)
>pulse
> PulseAudio Sound Server
>default
> Default ALSA Output (currently PulseAudio Sound Server)
>
>
>This gets more interesting comparing the sound modules loaded in
>the 3513
>install and the R14 install:
>
>3513:
>
>Module Size Used by
>snd_intel8x0 22768 2
>snd_ac97_codec 89868 1 snd_intel8x0
>ac97_bus 874 1 snd_ac97_codec
>snd_pcm 61237 2 snd_ac97_codec,snd_intel8x0
>snd_page_alloc 5901 2 snd_intel8x0,snd_pcm
>snd_timer 14902 1 snd_pcm
>snd 44394 8
>snd_ac97_codec,snd_intel8x0,snd_timer,snd_pcm
>soundcore 4378 1 snd
>
>R14:
>
>Module Size Used by
>snd_intel8x0 23757 0
>snd_ac97_codec 89404 1 snd_intel8x0
>ac97_bus 878 1 snd_ac97_codec
>snd_pcm 63880 2 snd_ac97_codec,snd_intel8x0
>snd_page_alloc 5978 2 snd_intel8x0,snd_pcm
>snd_timer 14946 1 snd_pcm
>snd 44598 4
>snd_ac97_codec,snd_intel8x0,snd_timer,snd_pcm
>soundcore 4386 1 snd
>
>They are identical, so what ever is going on with R14, it has
>exactly the same
>modules loaded and available that 3.5.13 does, but for some reason
>it is not
>seeing the sound card or anything associated with it.
pulseaudio: I know nothing and hope to keep my life that way. :)
If the aplay command responds then you have ALSA installed. (I
thought ALSA and pulseaudio were incompatible.)
Try this:
alsactl init
Also in KControl->Sound & Multimedia->Sound System, verify the
sound system is enabled in the General tab, then look in the
Hardware tab for the audio device selection.
Darrell
>I don't currently, but I'll build tarballs for my 3.5.13 tree and
>we can
>compare. I have old 3.5.13 installs from 2012, we could do that
>without
>additional effort (should be the same -- no?)
While I have a 3.5.13 and 3.5.13.2 partitions, they are not full
build sets. Just the basic main packages so I can conduct
comparison testing. Any effort I make to compare files would be
incomplete.
If you read the R14 release notes you'll see several new packages
added since 3.5.13.2. Those apps will have files in
/opt/trinity/bin(lib), but we don't care about them because we only
want to derive a list of naming changes since 3.5.13.2.
Darrell