messages printed after login?

messages printed after login?

[Igor Gueths]

Hi all. Whenever I login to a new TTY I keep getting stuff like the
following: c0288010 get_option_Rsmp_b0e10781
c028805c get_options_Rsmp_0fbff9b9
c0288170 rb_insert_color_Rsmp_aa2b5a22
c02883b8 rb_erase_Rsmp_da226a80
c0288490 rwsem_down_read_failed
c02885d4 rwsem_down_write_failed
c0288714 rwsem_wake
c028a290 zlib_inflate_workspacesize_Rsmp_ce5ac24f
c028a438 zlib_inflate_Rsmp_64cf8602
c028a41c zlib_inflateInit__Rsmp_456e911d
c028a32c zlib_inflateInit2__Rsmp_5d3b34e2
c028a2f0 zlib_inflateEnd_Rsmp_9ef45f92
c028a828 zlib_inflateSync_Rsmp_34582e0d
c028a298 zlib_inflateReset_Rsmp_ef76d642
c028a900 zlib_inflateSyncPoint_Rsmp_41d10449
c028aa5c zlib_inflateIncomp_Rsmp_b5058135
c028cabc zlib_deflate_workspacesize_Rsmp_f0caf44b
c028bacc zlib_deflate_Rsmp_28c35bd1
c028b550 zlib_deflateInit__Rsmp_c5e78d3e
c028b578 zlib_deflateInit2__Rsmp_262f9b2a
c028bd3c zlib_deflateEnd_Rsmp_cd8db61d
c028b8f8 zlib_deflateReset_Rsmp_8abb5b63
c028bd80 zlib_deflateCopy_Rsmp_fd39628f
c028b97c zlib_deflateParams_Rsmp_9088bbb2

These look like calls to zlib_deflate, and the beginning part looks like
an I/O address where a device would be, however I'm not sure what would
influence such behavior. I have never seen this before in all the times
I've rebuilt/tinkered with various kernels. I'm currently running
Kernel-2.4.22 with Debian-3.0R1. Does anyone have any idea what's causing
those messages to be printed? Thanks!

error starting emacspeak under red hat 9

[Jared]

Does anyone know what the following error means? i've gotten it on my laptop
running red hat 9 no package updates, and my friend gets it on his desktop
also running red hat 9 with no package updates. We have very different
hardware configurations, so I assume its a problem more then just us are
having. If I type
emacspeak
from a turminal with in x-windows, i get the following error
process speaker not running
Appreciate any help as a quick google search turned up nothing, and it
sounds like the emacspeak list is an unforgiving place for newbies.
appreciate any help.

Re: error starting emacspeak under red hat 9

[Guy Abandon.]

<<process speaker not running>>

I get this one without being in an X-Windows environment and put it
down to lack of configuration either with a suitable speech engine
part or similar.


<<sounds like the emacspeak list is an unforgiving place for
newbies.>>

I found that too, which is why I still don't use Emacspeak yet.

I downloaded but didn't get to try the Oralux distro yet either which
is meant to boot and work right out of the box so to speak.  Has
anyone made that work like that?

Is there any mileage in trying to get Emacspeak to run with an
existing Apollo that is already being driven by Speakup?
Is it worth using plain old Emacs and skip the speak bit?

We're meant to be Speakup users here, so who uses Emacspeak or Emacs
and how successfully?

GA!

Re: error starting emacspeak under red hat 9

[John covici]

Well, there are ways to use emacspeak with the same synth as speakup,
but they are unsupported and what I would suggest is that you buy the
$50 dectalk runtime for linux -- that will work with emacspeak and
you can have both at once.

Now I have found personally that speakup gives good feedback and at
least with the cvs version emacspeak is not necessary, but that is a
personal choice and you should play with it and see what you like.

on Wednesday 09/24/2003 Guy Abandon.(text.tools@virgin.net) wrote
 > <<process speaker not running>>
 > 
 > I get this one without being in an X-Windows environment and put it
 > down to lack of configuration either with a suitable speech engine
 > part or similar.
 > 
 > 
 > <<sounds like the emacspeak list is an unforgiving place for
 > newbies.>>
 > 
 > I found that too, which is why I still don't use Emacspeak yet.
 > 
 > I downloaded but didn't get to try the Oralux distro yet either which
 > is meant to boot and work right out of the box so to speak.  Has
 > anyone made that work like that?
 > 
 > Is there any mileage in trying to get Emacspeak to run with an
 > existing Apollo that is already being driven by Speakup?
 > Is it worth using plain old Emacs and skip the speak bit?

-- 
         John Covici
         covici@ccs.covici.com

Re: error starting emacspeak under red hat 9

[Guy Abandon.]

<<suggest is that you buy the
$50 dectalk runtime for linux -- that will work with emacspeak and
you can have both at once.>>

I approve of this and have considered it often enough and will more
when wallet permits.  I've read criticisms though even then that it
lacks the level of control you have with real hw synths like the
Apollo I have.  Not being able to interrupt and shut-up output would
annoy me.

Would this level of use of the sound card get in the way of using the
sound for sound's sake....   like the jukebox facility I've been doing
these past few weeks.  It's taking this long to load it with all the
CD's I have here.

I have another spare box though, so might keep jukebox as just that
and start again with a Slackware work machine.

GA!