Ticket #119 (closed defect: fixed)
bristol does not save its state on studio save
| Reported by: | http://distrozapper.myopenid.com/ | Owned by: | - |
|---|---|---|---|
| Priority: | major | Milestone: | 0.3 (preview 3) |
| Keywords: | Cc: |
Description
bristol does not save its state on ladish's SIGUSR1 (save studio). According to ladish logs this seems due to the fact that ladish uses the "first grandchild's PID", but the really valid PID is the one right after the fork.
Sending SIGUSR1 manually to the (really valid) bristol process results in a correctly saved mem file in ./~/.bristol/memory/<synth>.mem.
My environment:
gentoo 2.6.34-r12 64bit
ladish changeset a5d878cdc4363738db31c771dace7c14c4c75d3b
Bristol 0.60.7
Steps to reproduce:
1) Create a studio containing only bristol with commandline
startBristol -log -jack -b3
Name = "B3"
"run in terminal" unchecked
"Level 1" checked
2) Start studio, change something in bristol/B3's GUI
3) Save studio...nothing is saved in /home/<user>/.bristol/memory/hammondB3
4) Retrieve the PID of bristol and send a SIGUSR1 to it manually.
Now bristol saves a mem file.
I attached a ladish logfile.
Cheers
Robert
Attachments
-
ladish_bristol.log2
(41.4 KB) - added by http://distrozapper.myopenid.com/
2 years ago.
- ladish log on bristol studio save
