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
>And... the only reason I got a working printer is I made myself a
>member of the
>'sys' group otherwise creation of /etc/cups/printer.conf would
>have failed due
>to lack of permission. Since I was a member of the sys group,
>permission for
>cups operation was satisfied, however, apparently printer driver
>generation with
>the 'foomatic-db-generation' package uses another scheme prompting
>the error.
>How to solve for a normal user?
I believe users have to be a member of the lp group. Perhaps that
is the root cause of the problems?
Darrell
>Hah - knew it. Story of my life...
Be aware when you update your local repo that you have to update
your build script configurations for sip4-tqt and python-tqt.
Slavek and Francois snookered all of us with some patches. :)
I've updated my build script environment. Copy those build scripts.
The full grimy details are in bug report 1790.
Darrell
> That raised the question, do we have a list somewhere of what
>has been
>renamed? Some things have been renamed 'k'->'t' others 'k'->'tde'
>others not
>renamed at all. Doing 'tcmshell --list | sort' somewhat
>exemplifies the problem.
Do you have a full install of 3.5.13.2? If yes then grab a list of
/opt/trinity/bin and /opt/trinity/lib. We then can diff that list
to R14.
Darrell
>A bit strange, but yes, I now have the cups.sock interface, but I
>have a catch
>22 that prevents remote printer setup. As a user, you do not have
>sufficient to
>generate ppd files for this printer at home (normal HP Laserjet
>4). In
>administrator mode, after selecting the printer and pressing
>'Next' the select
>printer driver page loads, but the Manufacturer List and Printer
>List are blank
>-- nada....
>
>Have a look:
>
>That's one I can't explain. (1) user sees manufacturer and
>printers, but can't
>gen the ppd, (2) root just can't see the printer in order to be
>able to generate
>the ppd file. (God I miss the days of just selecting the PPD
>instead of a
>autogenerate on the fly scheme...)
>
>Any thoughts?
Share the exact steps.
That you see a list of available printers probably means CUPS is
configured correctly.
My printer is connected as a network device. After you share the
exact steps I'll try to duplicate here.
Darrell
>As I mentioned, a side effect of the processing git log in the
>proposed script
>is that each commit is on output in a single line. This would be
>possible to
>simply add the pagination.
>
>For example - adding one simple "sed" to a previously sent crazy
>command for
>listing on the console... see attached script.
Okay. Thank you. :)
Darrell
>Hmmm.. No release notes :(
>
>How long ago did you push them? My first build was on tarballs
>from 1/15 -- and
>I got not releasenotes. They come from tdebase correct?
Commit 32f7a85c, 2014-01-19.
Looks like you are 4 days late and a dollar short. :)
Darrell