Can anyone help ?

I tried following the instructions at http://rtcomm.garage.maemo.org/#install2
in order to install the IM messaging software.

I entered red pill mode as suggested and successfully downloaded and installed the RTCom Installer Beta. Then, when I then tried to run it, from Applications/Setting/Extras it didn't seem to do anything...

So, having decided to quit, I then tried to exit red pill mode ... and then hit the problem.

I discovered that Application Manager was now misbehaving. When I hit Application Manager/Tools/Application Catalogue , instead of letting me add a catalogue (or go therough the process to select the blue pill) it just tells me 'Operation already in progress' !!!

I've tried waiting, switching off and on again, but it still behaves the same. I guess perhaps Betas and red pills are beyond me

Can anyone help ???

Or is it just a case of reflash OS2008 and start again from scratch ?
Thanks.

Walter

Well, after a day of work somehow I finally got the OS2008 IM Upgrade installed.

If you have this same problem, maybe switching it off and leaving it a while and then trying again is the answer...but I'm really not too sure.

At least I didn't have to reflash...

I have the exact problem after Application Manager crashed during an installation. I can still install files fine, but I can't change the settings on it. On a side note, my Browser crashed during the installation also and was acting up, not downloading files and I was able to fix it by deleting the .mozilla from /home/user.
Edit/Delete Message

Hi, Wally.

I suffered a similar difficulty, with the Application Manager refusing to install applications from over the network due to 'Operation aready in progress'. I also suffered a crashing web browser around that time. I wasn't in red-pill mode.

I had to shutdown and pull the battery for about a minute in order to eliminate the problem. A simple power cycle was not enough. I'm conjecturing that was because of a temporary filesystem that does not necessarily lose its state on a power cycle.

I analysed the filesystem for files related to apt and dpkg, and removed any that appeared to be locks or transient working files. For example, one of the the following two files gave me a clues as to when the 'already in process' condition became asserted on the filesystem.

/var/lib/dpkg/lock

/var/apt/cache/archives/lock

Using the date from one of the suspicious lock files (I can't recall which - my terminal history isn't deep enough for me to recover it), I further analysed the filesystem for files with the identical timestamp, using a command like the following and being careful to specify identical whitespace in the grep expression. (There's probably a more proper way to do this search, using find, but this worked.):

ls -lR / | grep "Aug 8 18:31"

That search indicated the presence of symbolic links pointing to named pipes related to apt on a temporary filesystem (I also cannot recall which one). I shutdown, pulled the battery for about a minute, rebooted, and voila, problem solved.

Norm.