On Wed, 26 Nov 2003, Andrew A. Gill wrote:
> On Wed, 26 Nov 2003, Richard Guenther wrote:
> >
> > Uh. Suppose you're starting glame, not cglame, it should create one for
> > you - in fact it should pop up the preferences dialog the first time you
> > start glame and on such errors, too.
>
> It did, but it didn't generate a swap file.
It should, or glame will be terminated afterwards. Hint: go to the
swapfile tab and change location of the swapfile - it's probably way
wrong.
> > For cglame you need to run cglame -c /path/to/swap to create the swapfile.
> >
> > Hope this helps,
>
> It did.
>
> More or less. Now I get the following error in glame (looks
> like cglame will work):
>
> ALSA lib seq_hw.c:446:(snd_seq_hw_open) open /dev/snd/seq failed: No such
> file or directory
> open_alsa_sequencer: Error opening ALSA sequencer.
> midi_in_alsa_register: Couldn't open alsa midi sequencer
> loading /usr/local/share/glame/scripts/glame.scm
> /usr/local/share/glame/scripts/resample.scm: uncaught throw to
> glame-error: ()
> /usr/local/share/glame/scripts/bassboost.scm: uncaught throw to
> glame-error: ()
> /usr/local/share/glame/scripts/write_mp3.scm: uncaught throw to
> glame-error: ()
These are harmless. You probably dont have libfftw installed.
> GLAME testsuite
>
> Available tests are
> swtest-all -- swapfile subsystem checks
> test-filter-all -- filter/plugin checks
> test-gpsm-all -- gpsm midlayer checks
> Run all tests with (test-glame)
>
> loading /home/superluser/.glamerc
> update_preferences: Preferences:
> Swapfile directory /home/superluser/.glameswap
> Undo stack depth is 5
> Audio input plugin audio_in, device "plughw:0,0", rate 44100
> Audio output plugin audio_out, device "plughw:0,0"
> GLAME_WBUFSIZE 1024
> Popup timeout is 200ms
> Mac mode is off
> gui_main: path: /home/superluser/.glameswap
> WARNING: Unclean swap - running fsck
> cluster_cleanup: SWFS_CLUSTER Statistics: 0 gets, 0 lru hits, 0 misses
> cluster_cleanup: 0 meta reads, 0 meta writes, 0 data creates
> WARNING: Fsck successful
> Xlib: sequence lost (0x10000 > 0x29f) in reply type 0x1!
> Xlib: unexpected async reply (sequence 0x0)!
> Xlib: sequence lost (0x11fff > 0x29f) in reply type 0x8!
> Xlib: sequence lost (0x10240 > 0x29f) in reply type 0x3!
> Xlib: sequence lost (0x1200a > 0x29f) in reply type 0x60!
> Xlib: sequence lost (0x10000 > 0x29f) in reply type 0x0!
>
> Gdk-ERROR **: The program 'glame' received an X Window System error.
> This probably reflects a bug in the program.
> The error was '234'.
> (Details: serial 8191 error_code 234 request_code 0 minor_code 207)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error()
> function.)
> aborting...
Well - this is of course "interesting" ;) I'd be interested where this
happens, just try to run glame from inside gdb and do a backtrace.
Probably a gnome2 related thing (we didnt yet fully switch over from
gnome1 to gnome2 and use a lot of legacy stuff). Also tell us more about
your system - I suppose its debian unstable?
Maybe you could even track down the problem and fix it 8)
Thanks,
Richard.
--
Richard Guenther <richard dot guenther at uni-tuebingen dot de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/
|