Yes, I did wrong. I upgraded having devel repo on use. Result: First noticed that soma radio crashes on start. Now noticed that cutetube2 crashes on start. And cssu appdownloader crashes on start. I uninstalled all and installed back but they still crash and when I installed cssu appdownloader it said that "cannot install". It still installed it but it crashes.

So the upgrade has changed something necessary. Does anyone know what it could be or how to find out? I have also noticed since I started with N900 that on updates with console in the end there comes lines "should be 1.3 but found " without further stating what version has been found. But that has not really been of any problem before I think.

I would really appreciate any help (mocking of me of my already obvious stupidity is not the best help but if it is the price for getting help you are free to do it also). I'm like the guy hired to test what can go wrong except that no one hired me. But helping me may still benefit the community.

So what I have done to get here is that I have installed both cssu testing and devel enablers, made an upgrade with devel repos on use (cssu devel, extras-devel and extras-development) and then apt-get -f install (probably also apt-get --fix-missing). Yes, it is like shooting with a shotgun yourself. I'm running cssu testing with power53 kernel and overclocked with batterypatch to 805 (this is not an overclock problem which starts on 950 with my phone).

Are there some right commands to check from right places to show the right files needed for cssu working properly? Or is there some obvious packet to remove or to install or make re-install? All this stuff is unknown to me. Application manager installs fine other than testing apps and they seem to work.

I will try now installing the appdownloader through console if it would tell me something more.

Edit: Appdownloader was installed with apt-get without any alerts that I got with application manager but still it just crashes on start.

I tried to install cutetube2 through console to see what errors it gives. Well a lot of dpkg errors and said that /usr/bin/dpkg gave error code 1. Ok, so if I go to see /usr/bin/dpkg I will find what causes these problems. Was I supriced to see what was in there! Is this some kind of a joke, do I need a tool to read some scripts right or is there an elf living in my N900?

wow man...

I completely understand why you don't want to hear any jokes ...
and there are about 50 in me screaming to get out right at this moment...

But I will refrain.

I would suggest doing a complete scrub.
Reflash ...and start again.

Its fine to enable devel and development for download / installation of the progs and bits and pieces you need...
But staying in devel is not a good idea...
especially using term afterwards to affect change that draws on devel and development ...

apt get force install is normally akin to trying to getting the "prize" back into a box of cereal ....without dumping the all the cereal into a big bowl first...and without the box being "bag" shaped afterwards.
It is a blunt tool in the toolbox ...force install...

...mmm

I would say your "apt-get fix missing" definitely also pulled from devel / development ...
and it worked...
as the screenshot shows ..
it "fixed the missing " very well.

I don't want to reflash because I already know how to do that. But I don't know what was broken now or how to either fix it or prevent it from happening again. I think I could learn now a lot, maybe to opt out wrong packages when updating or upgrading and probably also learn where different kinds of stuff is stored and how to get it and install to right places.

Now I think this could be some kind of qt problem or then something else. But you mentioned the 'force install'. Have to say that from the way you use words makes it sometimes hard for me to understand correctly what you mean. Like now I'm not 100% sure do you suggest me to force install appdownloader or the other apps or not.

But I hope to learn how to make upgrade without breaking anything. Now I made the uppgrade and almost everything seems to work. It would not need a lot to learn how to prevent this to happen also to others.

Sorry for any confusion there Maemish...
I know some folks may throw around the usage of force install casually...
But if something doesn't install right in the first place the proper way ..
Taking a wrong puzzle piece and a mallet and beating a piece into place that never was meant to fit that way...
Is perhaps a better imagery to use.

I don't force install anything ....personally.
nor do I leave devel or development enabled while issuing terminal commands to update fix missing ...

I can't be 100% sure...
Since you haven't given a blow by blow account of everything exactly done...from the moment of reflash.
(Personally I video and say what I am doing next ...then pause it until the next step of whatever I am doing next...it is easier than writing it down...and better than audio...and I can flip through it to see what I did where and narrow down cause and effect...and be certain what the cause and effect are ...)

And I don't gamble unless the odds are definitely in my favour..
and Maemish man ...leaving devel /development enabled and doing what you have done with "fix missing" ...and goodness knows what else you have done before that.... not documented ...
you said it yourself ...
"I don't know what was broken now or how to either fix it or prevent it from happening again"
I can point to devel and development still enabled while playing with term as a certainty of the reason.
Definitely I could point to "cause and effect" here.

If you also do not know exactly what caused this ..it also means a documentation issue ...
if you go off site and do stuff that no one else does or isn't normally prescribed methods or is experimental and there isn't much info on cause and effect except warnings....
You need to be thorough in documentation .
I know you know how to reflash already.
That isn't the point.

I suggest you reflash and start over with exacting documentation ..
It is easier to hit the record button every time you go to do something... than writing it down ....or not recording it at all...
and test the n900 in between ....every experimental thing you are doing...
to make sure you nip issues where the start.

and it isn't exactly a desirable thing to do...reflash...reflash and reflash again..
But when experimenting ...one gets used to doing it over and over ...while working on a puzzle...so you can replicate the failure using a clean and documented device...as much as replicate the success using a clean and documented device.

Hear hear. Just hoping someone who knows about those things will be like: "Hey, it could be this or that and you could use this command and give the output so I can tell which parts contradict how it should be as I have on my output". I'm a believer so I believe almost everything is possible and that when you share what you know and do it affects that others share and do too. Not that people here would not be doing or sharing all the time and since the time being. I just wait and see if magic happens. Just had from one member here a message concerning one other stuff which fullfilled that what I had believed and waited to happen. You share and trust and sometimes it just works.

and even so...
but any help in the form of solutions ...at this point ...coming from others.... will be guessing on their part, without you offering blow by blow documentation of what you did.

The only thing that sticks out ...that with certainty I can point to...that you said ...is you have been doing term stuff while keeping devel and development enabled...
which is not a good idea at all...
it is known to be a big contributor to problems like what you are currently facing.

Past that ...
I would be irresponsible and cavalier with YOUR device ...
If I offered advice on how to solve a problem ....running on "guessing" what your problem is ...with zero documentation to go on.

I fully concur with what @endso is saying; using apt on console with multiple repositories that are not coherent together is asking for trouble. There are lot of packages with dependencies written so that dpkg thinks it can fulfill but end up with conflicting requirements. And if something does not cleanly install then adding --force will just make the install succeed without pulling in needed packages...

And regarding the elf you suspect that's burrowed into your device, yes; in fact there's a whole elfin family living in there...

hahaha
elfin family...
that is good juice...

I prefer smurfs ...
and think of myself as a n900 Gargamel

So accurate punning aside.

The sanest advice you will hear on your problem is this Maemish...

Do a reflash.
Document everything if you do from the beginning....including your reflash...
So you have a bulletproof step by step of what happened where.
You go "off site" (as I like to call it...) and start experimenting ...then you have full documentation of what happens where.
The bad...and the good...
your unfavourable or favourable results can then be replicated .
your problems or successes can pin pointedly be scrutinized by those who can help ...and they SEE where the error or benefit originated.
Otherwise you are just "lucking out" with successes you have no idea how they occurred or how to replicate them...
or..
you are stuck in a mess ...likewise with no doc as to how exactly you got there...hoping someone says "Try this _____ ..." ....where they have no more clue than you as to what the hell results will occur from the trying...
THAT is Russian Roulette my friend.
And you are doing it with your n900 ...
which could end up in far worse shape than a simple reflash may ever fix.

Also...
sure install from devel and development ...
Know the risks of whatever you install and what conflicts there may be with other things already or you intend to install.
If there are no stated risks with what you are installing from devel / development cats. ...and you discover a conflict that creates issues on your n900...
you then have the documentation to show what interacts badly with what...
and you can post that as a certainty ...and a warning for others to avoid.
Then...reflash and follow your own docs to the point just before the problems began...
and continue with your experimentation.

And lastly ...
Don't go leaving devel and development enabled after installing something successfully ..
disable devel cats and re enable say ...reg cats ...again..
and don't utilize and install from different levels of cats at the same time...
normal extras ...testing extras and devel really need to keep their distance from each other ...
Don't enable any 2 or all 3 levels of cats at the same time and install stuff.
and playing with term and apt-getting or apt fixing is wielding a very big stick ...know exactly the effect of doing so are before just doing it...
and know what cats you have enabled at the time...

for example...JUST like any linux distro...when you install the system you choose during install which level of cats you want to pull from...regular stable cat , testing, or developmental / bleeding edge ...
But changing cats to install this or that from different levels ...will set you up for potential conflicts...
if you have stuff installed from various levels ...reg. testing and development ...on your device...and you properly enable say regular extras ...after installing from testing or devel cats ....and then you apt-get or apt fix or apt whatever...it is going to pull in what is needed from the regular extras , ...and most likely will conflict across the board with whatever you have installed that could conflict...from testing or devel. ... get it?
It will try to add packages for a prog that may or will have the same requirements for other progs for testing and devel progs ...but a different version...or your testing and devel progs may be required to purge ...purge and flush simultaneously others...and make a big mess you cannot unsnarl ..
You can do everything right Maemish... but because you are utilizing across possibly 3 catalogs ...using apt ...in any general format ...is going to have repercussions that are massive ..
If you wish to experiment....and use apt.
Stick to one level of cats...2 at the most.....and keep them close...like stable and testing...or testing and devel.. and never install from the others...if you intend on swinging a big apt stick...
It will limit the damage ...
but with even 2 different cat levels ...expect damage ...
It won't be as bad...as 3 levels of cat programs ...but you will still have damage..

In fact...
I am sure there are warnings about utilizing the different cat levels...
as well as warnings about how to use apt...
for the n900

For sure..
I for sure know that another individual just recently hit the install "all" button for 64 repos ..
enabling every possible conflicting cat , empty cat ...and dead cat along with it...
creating chaos for his cats.
This person was paying attention to only part of the instructions and not the whole...nor followed through with the warnings...
I pointed out what he needed to read ...

But I think for both of you ...
to quote Dr Strange...
"They really should put the warnings at the beginning of spells..."