Windows Autoclosing & Shell Autoexiting At Resume!

[Micla]

Hi,

Coming back to try to use pdaXrom after a long time without Z and then without pdaXrom, I discover a bug which is really sufficient to disgust anybody ...

I've just installed PdaXrom (beta 1 - because all the threads that I've read seem to indicate it as the last one with a correct APM). And I discover a bug which I had met in the past, but I don't remember how I handled it, since I'm sure not to have been so much embarassed as I'm now :

At nearly each suspend-resume, my Z closes some or all the opened windows or underlying applications, and in pure initial shell environnement (before any "startx" command), I have seen a "logout" done just when resuming ...

Well, this is not quite comfortable to work ...

Would anybody have an idea ? (Sorry for such a basic thread compared with several "intergalactical" other ones around  ...)   :-)

Thx by adv,

Micla.

[T3_slider]

Well, to say something very simple, you should suspend by holding the On/Off button for 0.75 seconds and resume by pressing and releasing the Home button (and NOT the On/Off button) [at least this is the way to suspend/resume on a C1000-C3200].

As for more than that, you're probably going to have to fight with it.

[Micla]

A new element : several new tests show that things are not so simple :

This phenomenon seems to be linked to my CF card (SanDisk 512Mb Ultra II) : when I suspend resume with a simple shell window with a current directory on the CF, this window can be shut unexpectedly after a suspend / resume. In the same way, a window with an application opening a file on the CF card may be shut at resume. Instead, when the window has no relation with the CF, there is no (less ?) pb (during the tests made recently).

The problem is that I've found no clear & repeatable situation to reproduce the bug.

Would anybody know any problem about the relation betweeen suspend/resume & CF ?

Is it due to some bad settings ? Or to a bad CF ?

[danr]

Is it due to some bad settings ? Or to a bad CF ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160857\"][{POST_SNAPBACK}][/a][/div]

On suspending the Zaurus, the CF card is automatically ejected, which causes the problems you see.  I only use my CF card for storing files rather than as a target for installing software, and use an SD card for software instead, as it doesn't have this issue.

The CF auto-eject may have been fixed in the 2.6 kernel though - anyone have any information on this?

[T3_slider]

You can always prevent the CF card from being unmounted by modifying the suspend/resume scripts in /etc/apm/

I'm absolutely no expert on this, so don't ask me how to do this (I would suspect you could alter the file /etc/apm/scripts.d/cardctl but don't quote me on it), and it may waste a little battery power, but it can be done.