Hi

because of troubles with Rosegarden for 64 Studio 2.1, I'll try to use
Qtractor with 64 Studio 3.0. As long as 64 Studio 3.0 isn't released,
I'll run Qtractor and Fluidsynth-DSSI under Suse 11.0, but there seems
to be problems for Fluidsynth, because when running Qtractor and Qsynth,
I also get much too often crashes.

It doesn't matter what I run, Rosegarden under 64 Studio or Suse, or
Qtractor under Suse. It's not clear which application will make the
systems unstable, but running jackd and Qsynth alone under Suse, let
Qsynth crash.

The used hardware, when I did the debugging:

Mobo ASUS M2A-VM HDMI
BIOS version 2201
On-board sound and HDMI are disabled, the HDMI card is removed
The on-board ATI Radeon X1250-based graphics is controlled by the VESA
driver
CPU AMD Athlon BE-2350
Sound card TERRATEC EWX 24/96
Swissonic USB MIDI device, 1 input, 1 output
RAM 1024 MB + 1024 MB - Framebuffer 128 MB

What I did before debugging and when I debugged, also the versions of
the relevant applications and other relevant information for the Suse
install:

Note: When I made test or tried to make music, I used different versions
for some software, different kernel-rt and BIOS versions.

/etc/security/limits.conf
@audio - rtprio 99
@audio - memlock unlimited
@audio - nice -19

kernel-rt 2.6.25.18-0.2-x86_64 from openSUSE-11.0-Updates
alsa 1.0.16-39.1-x86_64 from repo-oss
alsa-firmware 1.0.16-24.1-noarch from repo-oss
jack 0.109.2-36.1-x86_64 from repo-oss, before the debugging I downgraded to
jack 0.109.2-0.pm.1-x86_64 from http://ftp.skynet.be/pub/packman/suse/11.0/
some days ago the BIOS version was 2101, while fluidsynth and
libfluidsynth1 were 1.0.8-50.1-x86_64 from repo-oss
actually fluidsynth and libfluidsynth1 are 1.0.8-0.pm.1-x86_64 from
http://ftp.skynet.be/pub/packman/suse/11.0/
qsynth 0.3.3-0.pm.1-x86_64 from http://ftp.skynet.be/pub/packman/suse/11.0/

This applications didn't run, when I debugged:
fluidsynth-dssi 0.9.1-188.1-x86_64 from repo-oss
qtractor 0.2.2-0.pm.1-x86_64 from
http://ftp.skynet.be/pub/packman/suse/11.0/

I turned on the monitor and the computer.
I booted Suse 11.0 and started a KDE3 session.
I run KPowersave, CPU Frequency Policy: Performance.
I run Konsole.
I run su, 2 times ntpdate, Ctrl+D for exit.
I run Thunderbird and created a new messages for this report.
I run Firefox.
I run hwinfo --help and hwinfo --memory.
I run Konqueror file browser.
I run uname -r.
I run YaST2 GUI, resp. just Package Manager and Repository Manager.
I closed Konqueror.
I closed YaST2.

I started the debugging with making a core file for Qsynth.

Shell:

spinymouse@suse11:~> ls ~/.config/rncbc.org
QjackCtl.conf Qsynth.conf-BAK-01 Qtractor.conf
spinymouse@suse11:~> jackd -R -p1024 -dalsa -r48000 -p256 -n2 -D -Chw:0
-Phw:0
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|256|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback

I opened Shell No. 2 for Konsole and went on.

spinymouse@suse11:~> ulimit -c 10240
spinymouse@suse11:~> ulimit -c
10240
spinymouse@suse11:~> ulimit -c 10240
spinymouse@suse11:~> qsynth -v

Qsynth1

Setup... >
Audio > changed Sample Rate to 48000 and Polyphony to 16
Soundfont > loaded /mnt/music_sata/mix_vol_1.sf2/PC51f.sf2
OK > Yes

Added A New Engine, QSynth2

Audio > changed Sample Rate to 48000 and Polyphony to 16
Soundfont > loaded /mnt/music_sata/mix_vol_1.sf2/PC51f.sf2
OK

Added A New Engine, QSynth3

Audio > changed Sample Rate to 48000 and Polyphony to 16
Soundfont > loaded /mnt/music_sata/mix_vol_1.sf2/PC51f.sf2
OK

Added A New Engine, QSynth4

Audio > changed Sample Rate to 48000 and Polyphony to 16
Soundfont > loaded /mnt/music_sata/mix_vol_1.sf2/PC51f.sf2
OK

Disabled Reverb and Chorus for Qsynth1.
Disabled Reverb and Chorus for Qsynth2.
Disabled Reverb and Chorus for Qsynth3.
Disabled Reverb and Chorus for Qsynth4.

Options... > enabled ~/qsynth.log > OK

I got this new messages in Shell (No. 1):
subgraph starting at qsynth timed out (subgraph_wait_fd=9, status = 0,
state = Running)


**** alsa_pcm: xrun of at least 1227621106974.720 msecs

subgraph starting at Qsynth2 timed out (subgraph_wait_fd=9, status = 0,
state = Triggered)


**** alsa_pcm: xrun of at least 1227621106974.720 msecs

subgraph starting at Qsynth2 timed out (subgraph_wait_fd=14, status = 0,
state = Triggered)


**** alsa_pcm: xrun of at least 1227621106974.720 msecs

I guess this is ok, because of adding and editing engines for Qsynth.

QSynth1 > Channels > Changed Ch 1 Bank 0 Prog 0 to Bank 128 Prog 25 > OK
> (default) Save and closed this window

QSynth2 > Setup... > Soundfonts > loaded
/mnt/music_sata/mix_vol_1.sf2/Drums/Acoustic drum set.SF2, removed
/mnt/music_sata/mix_vol_1.sf2/PC51f.sf2
OK > Yes

QSynth1 > Setup... > MIDI > changed client ID to QSynth1 > Audio >
chaged Sample Format to float
OK > Yes
QSynth2 > Setup... > Audio > changed Sample Format to float
OK > Yes
I was thinking of taking a look if the client names for Qsynth MIDI and
Audio were fine, but before I could take care of this, QSynth crashed
and jackd was killed.

To the Shell (No. 1) messages was added:

subgraph starting at Qsynth3 timed out (subgraph_wait_fd=14, status = 0,
state = Triggered)


**** alsa_pcm: xrun of at least 1227621106974.720 msecs



**** alsa_pcm: xrun of at least 1227621106974.720 msecs

subgraph starting at Qsynth2 timed out (subgraph_wait_fd=21, status = 0,
state = Running)


**** alsa_pcm: xrun of at least 1227621106974.720 msecs

subgraph starting at qsynth timed out (subgraph_wait_fd=21, status = 0,
state = Running)
jackd watchdog: timeout - killing jackd
spinymouse@suse11:~>

To the Shell No. 2 messages was added:

Killed
spinymouse@suse11:~>

I closed Shell No. 2 and continued with Shell (No. 1).

spinymouse@suse11:~> cd ~/.config/rncbc.org
spinymouse@suse11:~/.config/rncbc.org> ls
QjackCtl.conf Qsynth.conf Qsynth.conf-BAK-01 Qtractor.conf
spinymouse@suse11:~/.config/rncbc.org> cp Qsynth.conf Qsynth.conf-BAK-02
spinymouse@suse11:~/.config/rncbc.org> ls
QjackCtl.conf Qsynth.conf Qsynth.conf-BAK-01 Qsynth.conf-BAK-02
Qtractor.conf

I opened Konqueror file browser. In the users home there is a file
qtractor.log, but it includes no messages for today and there also is no
core file. Without a core file, I can't go on with gdb, I only can add
the latest Qsynth.conf.

I started at ntpdate atom.uhr.de 25 Nov 14:56:17 and finished at ntpdate
ntp.favey.ch 25 Nov 19:14:05.

Cheers,
Ralf
[Presets]
DefPreset=(default)

[SoundFonts]
SoundFont1=/mnt/music_sata/mix_vol_1.sf2/PC51f.sf2
BankOffset1=0

[Settings]
DisplayName=Qsynth1
MidiIn=true
MidiDriver=alsa_seq
MidiDevice=
MidiChannels=16
AlsaName=Qsynth1
AudioDriver=jack
AudioDevice=
JackName=qsynth
JackAutoConnect=true
JackMulti=false
AudioChannels=1
AudioGroups=1
AudioBufSize=64
AudioBufCount=2
SampleFormat=float
SampleRate=48000
Polyphony=16
ReverbActive=false
ReverbRoom=0.200000002980232
ReverbDamp=0
ReverbWidth=0.5
ReverbLevel=0.899999976158142
ChorusActive=false
ChorusNr=3
ChorusLevel=2
ChorusSpeed=0.300000011920929
ChorusDepth=8
ChorusType=0
LadspaActive=false
Gain=1
Server=false
MidiDump=false
Verbose=true

[History]
MessagesLogPathComboBoxItem1=~/qsynth.log

[Geometry]
qsynthChannelsFormx=0
qsynthChannelsFormy=0
qsynthChannelsFormwidth=373
qsynthChannelsFormheight=240
qsynthChannelsFormvisible=false

[Preset]
Chan1=0:128:25
Chan2=1:0:1
Chan3=2:0:2
Chan4=3:0:3
Chan5=4:0:4
Chan6=5:0:5
Chan7=6:0:6
Chan8=7:0:7
Chan9=8:0:8
Chan10=9:128:0
Chan11=10:0:10
Chan12=11:0:11
Chan13=12:0:12
Chan14=13:0:13
Chan15=14:0:14
Chan16=15:0:15

[Engine]
Qsynth2PresetsDefPreset=(default)
Qsynth2SoundFontsSoundFont1=/mnt/music_sata/mix_vol_1.sf2/Drums/Acoustic drum set.SF2
Qsynth2SoundFontsBankOffset1=0
Qsynth2SettingsDisplayName=Qsynth2
Qsynth2SettingsMidiIn=true
Qsynth2SettingsMidiDriver=alsa_seq
Qsynth2SettingsMidiDevice=
Qsynth2SettingsMidiChannels=16
Qsynth2SettingsAlsaName=Qsynth2
Qsynth2SettingsAudioDriver=jack
Qsynth2SettingsAudioDevice=
Qsynth2SettingsJackName=Qsynth2
Qsynth2SettingsJackAutoConnect=true
Qsynth2SettingsJackMulti=false
Qsynth2SettingsAudioChannels=1
Qsynth2SettingsAudioGroups=1
Qsynth2SettingsAudioBufSize=64
Qsynth2SettingsAudioBufCount=2
Qsynth2SettingsSampleFormat=float
Qsynth2SettingsSampleRate=48000
Qsynth2SettingsPolyphony=16
Qsynth2SettingsReverbActive=false
Qsynth2SettingsReverbRoom=0.200000002980232
Qsynth2SettingsReverbDamp=0
Qsynth2SettingsReverbWidth=0.5
Qsynth2SettingsReverbLevel=0.899999976158142
Qsynth2SettingsChorusActive=false
Qsynth2SettingsChorusNr=3
Qsynth2SettingsChorusLevel=2
Qsynth2SettingsChorusSpeed=0.300000011920929
Qsynth2SettingsChorusDepth=8
Qsynth2SettingsChorusType=0
Qsynth2SettingsLadspaActive=false
Qsynth2SettingsGain=1
Qsynth2SettingsServer=false
Qsynth2SettingsMidiDump=false
Qsynth2SettingsVerbose=false
_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Hi Hermann

you noticed yourself, that you sent this mail 2 minutes before off-list .

> int
> main (int argc, char* argv[])
> {
> int * weh = 0;
> int oh = *weh;
>
> return 0;
> }

It's fine broken and I got a core file for my broken 64 Studio Lenny
install.

spinymouse@64studio:~/Desktop$ gcc textfile.c -o broken
spinymouse@64studio:~/Desktop$ ./broken
Segmentation fault
spinymouse@64studio:~/Desktop$ ulimit -c
0
spinymouse@64studio:~/Desktop$ ulimit -c 1234567890
spinymouse@64studio:~/Desktop$ ./broken
Segmentation fault (core dumped)

I'll test it later for Suse 11.0. I could do a Qsynth debugging for my
64 Studio 2.1 Etch, but it should work for Suse too.

Thank you,
Ralf

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

jackd and qsynth both were killed without being evident.

Is a core file written if the "crash" is a kill?

I run

spinymouse@64studio:~/Desktop$ ulimit -c 0

and now I can't change the limit any more

spinymouse@64studio:~/Desktop$ ulimit -c 1234567890
bash: ulimit: core file size: cannot modify limit: Operation not permitted

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

I'll go on later with debugging MIDI applications for 64 Studio and
Suse. What outputs will I get if I valgrind applications by running
"valgrind name-of-program program-arguments"? Are they acceptable for
bug reports too?

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Hi

* Good news
If the value for ulimit was set back to 0, than it's not possible
to set it again to another value, but this is possible again,
after the next startup.
* Bad news
spinymouse@suse11:~> ulimit -c
0
spinymouse@suse11:~> ulimit -c 1234567890
spinymouse@suse11:~> ulimit -c
1234567890
spinymouse@suse11:~> ./broken
Segmentation fault (core dumped)
spinymouse@suse11:~> gdb broken core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib64/libc.so.6...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `./broken'.
Program terminated with signal 11, Segmentation fault.
[New process 3674]
#0 0x000000000040045f in main ()
(gdb) where
#0 0x000000000040045f in main ()
Current language: auto; currently asm
(gdb) quit

Suse and 64 Studio create core files for "broken", it looks like
"qsynth" and "jackd" where killed because of an error, but without any
error. It might be impossible to get a core file. On the off chance that
I'll get a core file, did I used gdb correctly?

For a bug report I would copy everything between "(gdb) where" and
"(gdb) quit" and nothing else, right? I don't need to attach the core
file, but I need to keep it, if I get a request to run gdb with other
options, is this correct?

Cheers,
Ralf

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf Mardorf schrieb:
> * Good news
> If the value for ulimit was set back to 0, than it's not possible
> to set it again to another value, but this is possible again,
> after the next startup.

yeah, I noticed this strange behaviour too. It's sufficient to close the shell
and open another one. Of course, reboot fixes it too :-P


> Core was generated by `./broken'.
> Program terminated with signal 11, Segmentation fault.
> [New process 3674]
> #0 0x000000000040045f in main ()
> (gdb) where
> #0 0x000000000040045f in main ()
> Current language: auto; currently asm
> (gdb) quit
>
> Suse and 64 Studio create core files for "broken", it looks like
> "qsynth" and "jackd" where killed because of an error, but without any
> error. It might be impossible to get a core file. On the off chance that
> I'll get a core file, did I used gdb correctly?

yes, all done correctly.
You did run qsynth and jackd from a terminal on which you set the
ulimit -c unlimited prior to running them? But didn't get a core dump?
Then indeed it looks as if they got killed by a signal or it could be
an emergency shutdown triggered from within the applications. Anyway,
if an program actually crashes (segmentation fault or similar), you
should get an core file. If this isn't the case, I'd report this
behaviour and just ask the autor(s) how to proceed or what additional
informations they need.

> For a bug report I would copy everything between "(gdb) where" and
> "(gdb) quit" and nothing else, right? I don't need to attach the core
> file, but I need to keep it, if I get a request to run gdb with other
> options, is this correct?

Yes, just the callstack info is sufficient. In this small test example,
the stacktrace obviously lists just the main() function, because the
null pointer error in this example happens in the second line within main().
In a real world example, such a stacktrace could be several hundred lines of text.

Well, if the crash is sufficiently reproducible, you can even delete
the core, if disk space is an concern, but it could be a good idea
to keep it around. Indeed, using the core file, it's possible to look
for additional informations like the contents of some variables.

Cheers,
Hermann


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJMj75ZbZrB6HelLIRAl1fAKCjLrljxFLsERpy3e0HlB zMnFGgCACgjta6
QWlMHNygg0s/85lPiihU7kA=
=IxUT
-----END PGP SIGNATURE-----
_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Good morning Hermann

> yeah, I noticed this strange behaviour too. It's sufficient to close
> the shell
> and open another one. Of course, reboot fixes it too :-P

I was thinking of testing "just" to start a new session instead of doing
a reboot, but I didn't thought about just to close and open the shell,
because I'm most time using Yakuake, this terminal emulation starts with
each session and the terminal emulation will scroll down, when I push
F12. I seldom open or close a shell.

> yes, all done correctly.
> You did run qsynth and jackd from a terminal on which you set the
> ulimit -c unlimited prior to running them? But didn't get a core dump?
> Then indeed it looks as if they got killed by a signal or it could be
> an emergency shutdown triggered from within the applications. Anyway,
> if an program actually crashes (segmentation fault or similar), you
> should get an core file. If this isn't the case, I'd report this
> behaviour and just ask the autor(s) how to proceed or what additional
> informations they need.

Shell:

spinymouse@suse11:~> jackd -R -p1024 -dalsa -r48000 -p256 -n2 -D -Chw:0
-Phw:0
[snip]
jackd watchdog: timeout - killing jackd
spinymouse@suse11:~>

Shell No. 2

spinymouse@suse11:~> ulimit -c 10240
spinymouse@suse11:~> qsynth -v
[snip]
Killed
spinymouse@suse11:~>

The whole report is here:
http://www.linux-archive.org/64-studio-user/199594-problems-qtractor-debugging-qsynth-failed.html

Cheers,
Ralf

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf Mardorf wrote:
>
> I was thinking of testing "just" to start a new session instead of doing
> a reboot, but I didn't thought about just to close and open the shell,
> because I'm most time using Yakuake, this terminal emulation starts with
> each session and the terminal emulation will scroll down, when I push
> F1t12. I seldom open or close a shell.
>
When yakuake opens the first window that you can type in, it opens a
shell. You can open more with Ctrl-Shift-n and you can exit them by by
typing exit. Each of those Konsole tabs is its own instance of the
shell (yakuake is essentially a drop down version of Konsole).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJMma0wRXgH3rKGfMRAgWCAJ9Za4zw7TlknphhrdHQN/4tXs6bFgCgsFOD
eJUVF/9xMJK9FH24y8R/0Oc=
=kJqQ
-----END PGP SIGNATURE-----
_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Gustin Johnson wrote:
> Ralf Mardorf wrote:
> > I was thinking of testing "just" to start a new session instead of doing
> > a reboot, but I didn't thought about just to close and open the shell,
> > because I'm most time using Yakuake, this terminal emulation starts with
> > each session and the terminal emulation will scroll down, when I push
> > F1t12. I seldom open or close a shell.
>
> When yakuake opens the first window that you can type in, it opens a
> shell. You can open more with Ctrl-Shift-n and you can exit them by by
> typing exit. Each of those Konsole tabs is its own instance of the
> shell (yakuake is essentially a drop down version of Konsole).

Hi Gustin

thank you, but I know this, I also like Ctrl+Shift+T and Ctrl+Shift+L
but for the behaviour of ulimit I wasn't thinking about opening a new
shell. If people run Konsole, than they might close it and open it again
and than they will notice that ulimit is fine again, while I never close
Yakuake and not always open more than one shell.

By the way, Dolphin, the file browser that replaces Konqueror for the
KDE4, isn't as good in splitting, like the Konqueror file browser is.
Maybe KDE4 is appraised as advanced, because many people don't use the
features of KDE3, but use KDE3 as limited as Windows and GNOME only can
be use. I guess many features of KDE3 are unknown, like features that
are unknown for very old WMs, e.g. the different WMs that were available
for the Atari and that also might be the cause, why people think that
there are features for KDE4, that never existed for other WMs before.
But I have to admit, that there might be reasons, why features were not
taken over from KDE3 to KDE4. I still hope that KDE3 will be further
developed too. The first really good KDE3 is 3.5.9 and I won't believe
that with the first useful KDE3, they will stop going on with it, but
begin a new not full developed KDE4. Just my opinion. The only worse
thing for me about Etch is, that Etch has a KDE3 before 3.5.9.

Anyway, Lenny and Suse 11.0 still make KDE3 available.

Are you using Yakuake too? I never found something that is as good as
Yakuake. Tilda and others always were not fine for my Linux. I like to
have a shell available by just pushing a key.

Cheers,
Ralf

_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf Mardorf wrote:
> By the way, Dolphin, the file browser that replaces Konqueror for the
> KDE4, isn't as good in splitting, like the Konqueror file browser is.

It is pretty easy to change the default to be Konqueror again. Also,
they introduced Dolphin in one of the 3.5.x releases, it is not specific
to kde4

> Maybe KDE4 is appraised as advanced, because many people don't use the
> features of KDE3, but use KDE3 as limited as Windows and GNOME only can
> be use. I guess many features of KDE3 are unknown, like features that
> are unknown for very old WMs, e.g. the different WMs that were available
> for the Atari and that also might be the cause, why people think that
> there are features for KDE4, that never existed for other WMs before.
> But I have to admit, that there might be reasons, why features were not
> taken over from KDE3 to KDE4. I still hope that KDE3 will be further
> developed too. The first really good KDE3 is 3.5.9 and I won't believe
> that with the first useful KDE3, they will stop going on with it, but
> begin a new not full developed KDE4. Just my opinion. The only worse
> thing for me about Etch is, that Etch has a KDE3 before 3.5.9.
>
> Are you using Yakuake too? I never found something that is as good as
> Yakuake. Tilda and others always were not fine for my Linux. I like to
> have a shell available by just pushing a key.

I am using the kde4 version of Yakuake, but yes I am using it on my
Ubuntu laptop.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJMnCCwRXgH3rKGfMRAnSPAKCCyZlX6kPuAqhmzF4R3R zhzL1RZACbB6Qq
2GVf2etjC7FPLZYhJSgJbvg=
=GqoG
-----END PGP SIGNATURE-----
_______________________________________________
64studio-users mailing list
64studio-users@64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users