| 1 |
ok. I didn't realize that oocalc actually executed in your first attempt. |
| 2 |
Out of ideas then. |
| 3 |
|
| 4 |
FWIW - a few guesses: I'd execute oocalc under strace, and try to find |
| 5 |
what is killing oocalc (does it decide to exit, or is it sent some |
| 6 |
signal). If your suspecting xterm to be the culprit (i.e., yr script |
| 7 |
works-as-expected w/o the xterm wrap) then maybe it'll be worthwhile |
| 8 |
looking into the X resources yr xterm is reading. |
| 9 |
HTH |
| 10 |
Amit |
| 11 |
|
| 12 |
Mick wrote: |
| 13 |
> On Tuesday 16 March 2010 07:40:04 Amit Dor-Shifer wrote: |
| 14 |
> |
| 15 |
>> What does |
| 16 |
>> |
| 17 |
>> xterm -fg green -bg black -e 'gpg Personal/data.ods.gpg;echo $?' tell you? |
| 18 |
>> |
| 19 |
> |
| 20 |
> It doesn't return anything on the terminal I launch it from, but decrypts the |
| 21 |
> file in an xterm and then closes it (the xterm). So the gpg part works fine. |
| 22 |
> |
| 23 |
> |
| 24 |
>> I'm thinking that gpg fails, so oocalc never launches (because you |
| 25 |
>> conditioned its execution with '&&', and the script continues to shred the |
| 26 |
>> file. |
| 27 |
>> |
| 28 |
> |
| 29 |
> The gpg part does not fail, because when I run: |
| 30 |
> |
| 31 |
> xterm -fg green -bg black -e 'gpg Personal/data.ods.gpg && oocalc \ |
| 32 |
> Personal/data.ods' |
| 33 |
> |
| 34 |
> An xterm opens up asks for a passwd to decrypt the file, decrypts it and |
| 35 |
> launches OOo. However, the xterm dies immediately after that. |
| 36 |
> |
| 37 |
> On my x86 machine, the xterm stays open until I close OOo. This is how it |
| 38 |
> should work; i.e. the xterm should continue to run as long as any processes |
| 39 |
> within it are still running. |
| 40 |
> |
| 41 |
> This makes me think that it may be some env or profile difference ...? What |
| 42 |
> would control this behaviour in an xterm? |
| 43 |
> |
Archives