Re: [Fwd: FVWM: fvwmaudio & fvwmevent dump cores]

From: Thomas A. Gardiner <gardiner_at_pas.rochester.edu>
Date: Wed, 9 Jun 1999 13:14:27 -0400 (EDT)

I must be jinxed...
Performing the same chages listed below, and substituting for the sound
playing program as

AddToFunc "myplay" "I" Exec exec /usr/local/bin/play /usr/share/sound/$0

I've also tried substituting wavplay (the sound files are .wav files) with
the same result.

I still get a core dump. What's worse, the FvwmEvent man pages suggest
simple examles of using FvwmEvent, like echo-ing a string to the terminal.
Even this simple example from the man pages causes a core dump for me. Is
it possible I'm missing something big? or even little... I should say
that I'm trying this with fvwm2.2.046 and fvwm2.2.2

I'm going to dig through the FAQ again now for some simple examples of
using FvwmEvent, can anyone think of some which might be indicative of the
problem I'm having?

Thanks,


On Wed, 9 Jun 1999, Jacques B. Siboni wrote:

> Thomas,
>
> Michael's mail gave the answer. i confirm it works with fvwm2.2.2 event
> module. It was actually a configuration problem. The difference between the
> 2.2.2 and 2.3.3 is that the former dumps core with no explanations when there
> is a configuration problem although the latter keeps running.
>
> The result is that now I use the 2.2.2 package as is. So far I did not compile
> it as root and did not install it as root, I installed it on my home directory
> (using ./configure --prefix=<myhomedir>).
>
> One reason is that I run rpm version 2.0.46, the one provides with RedHat 5.2.
> The 2.2.2 was grabbed from fvwm.org
>
> I am using the Nextlevel M4 RedHat package. I have just put the fvwmEvent
> instructions in .fvwm2rc.modules here thay are:
> ######################FvwmEvent###########################################
> ##### FvwmEvent
> #*FvwmEventDir SOUND_DIR
> #*FvwmEventCmd SOUND_COMMAND
> *FvwmEventCmd myplay
> *FvwmEventDelay 0
> # User must add a new column to each line below, specifying
> # a sound file from SOUND_DIR (define-d in .fvwm2rc-defines)
> *FvwmEvent startup start.au
> *FvwmEvent shutdown cannot.be.completed.au
> *FvwmEvent unknown crash.au
> *FvwmEvent add_window gong.au
> *FvwmEvent raise_window door_open.au
> *FvwmEvent lower_window door_shut.au
> #*FvwmEvent focus_change long-beep.au
> *FvwmEvent focus_change thin.bell.au
> *FvwmEvent destroy_window robot_dead.au
> *FvwmEvent iconify piano-beep.au
> *FvwmEvent deiconify meepmeep.au
> ##*FvwmEvent toggle_paging gong.au
> *FvwmEvent new_page low-smash.au
> *FvwmEvent new_desk ding.au
> #*FvwmEvent configure_window drip.au
> *FvwmEvent window_name metal.au
> *FvwmEvent icon_name clink.au
> *FvwmEvent res_class chirp1.au
> *FvwmEvent res_name bubble1.au
> *FvwmEvent end_windowlist bass-snap.au
>
> *FvwmEvent error cowbell.au
> #*FvwmEvent icon_location say-beep.au
> *FvwmEvent map whip.au
> *FvwmEvent config_info ooh.au
> *FvwmEvent end_config_info monkey.au
> *FvwmEvent icon_file return.au
> *FvwmEvent default_icon whistle.au
> *FvwmEvent string jackhammer-short.au
> *FvwmEvent mini_icon hi.au
> *FvwmEvent windowshade hammer.au
> *FvwmEvent dewindowshade cuckoo.au
>
> I put the following lines in .fvwm2rc.init:
>
> AddToFunc "myplay" "I" Exec exec /usr/local/ltcbin/rugplay /usr/share/sound/$0
>
> AddToFunc "SetupFunction"
> + "I" Module FvwmEvent
>
> And I disabled sound events in .fvwm2rc.defines:
> # define(`WANT_SOUND_EVENTS')
>
> Cheers
>
> Jacques
>
>
> Michael Han wrote:
> >
> > Previously...
> > >Thomas A. Gardiner wrote:
> > >> I'm having the same problem as you... Red Hat 5.2 and FvwmAudio core
> > >> dumps do to a seg. fault. I see that you managed to get the audio working
> > >> by going to version 2.3.3. Did you have any success using the FvwmEvent
> > >> executeable with version 2.2.2 as Dominik Suggested?
> > >
> > >Yes it is perfect, it works fine ... so far ...
> >
> > Jacques, really what you're doing shouldn't be necessary. If I recall
> > your .fvwm2rc correctly, you're calling FvwmEvent explicitly, not
> > trying to recycle legacy FvwmAudio config. Try 2.2.2's FvwmEvent.
> > Hopefully it will work properly with your .fvwm2rc.
> >
> > Thomas, you had a question about the interaction with the M4 files on
> > your RedHat system. Take a look at the FVWM FAQ, which addresses this
> > question.
> > --
> > mikehan_at_best.com
> > I will not bribe Principal Skinner
> > - The collected wisdom of Bart Simpson
>
> --
> Dr. Jacques B. Siboni mailto:jacsib_at_Lutecium.fr
> 8 pass. Charles Albert, F75018 Paris, France
> Tel. & Fax: 33 (0) 1 42 28 76 78
> Home Page: http://www.lutecium.fr/jacsib/
> --
> Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
> To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
> message to majordomo_at_fvwm.org.
> To report problems, send mail to fvwm-owner_at_fvwm.org.
>

--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Jun 09 1999 - 12:17:07 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:02 BST