That's most likely unrelated. It means the file system is corrupted (when the kernel detects that it remounts it read-only as a precaution to avoid damaging it further).
There are many ways this can happen, like mounting on another computer via USB and unplugging without unmounting cleanly, unclean shutdown (removing the battery, or running out of battery suddenly) and so on. It may also be bug 2940 if you're one of the unlucky first buyers (though you would probably have noticed years ago), so check for that first.
Otherwise you should unmount the filesystem and repair it with dosfsck, it should be fine after that.
I don't think it's the kernel, if there's anything in the community that triggers it I would suspect the X server (I'm still not 100% sure I guessed the build flags correctly on that one).
Wow, I'm speechless (well, not really).
In spite of what the marketing says about the openness of maemo they won't even disclose the build flags.
Cannot say I'm really surprised.
I don't think it's the kernel, if there's anything in the community that triggers it I would suspect the X server (I'm still not 100% sure I guessed the build flags correctly on that one).
should be the right ones, I mean, autobuilder uses same..
Wow, thanks, that's exactly the info I was looking for!
Using the above I get exactly the same Xomap binary as before, so if there is a bug it's not due to build flags at least, good to know.
I hadn't seen "maemo-launcher" as an option before, but that explains some other differences I noticed in GUI apps. Unfortunately the deb tools in scratchbox are too old to handle "parallel", but a few packages deal with it on their own in debian/rules. I'll probably adapt others to do the same for sanity's sake.
libssl0.9.7 is not working after installing this SSU and I am using the stable version, when i try to install gizmo, it says that, and when i used -apt get, it said it installed, but when I tried gizmo again, it said missing libssl0.9.7 again, is this just me or other people too?
