Notices

Hi Wizink : as I said earlier,

you probably have some of the following :

+ devel (developers) repositories that have newer versions of components that are not official

+ old version of evas based demos

+ broken installation due to some corrupted package etc.

So my guide :

go to the application installer, install canola-cleanup, run it (it will delete and remove everything from canola)

Reboot the device (just for safety)

Then go to application installer and disable all non-official repositories.
If you can, leave only the nokias and the maemo extras and maemo repository.

Install canola, then enable your repositories again.

It has worked for the people with similar problem

hope this helps,

Marcelo

Thanks and I will try it! I appreciate your quick response and you dedication to solve the communities' endless flood of questions!

...and unfournately that did not work and the same error message pops up and even my application manager crashes! Installing from root is to no avail as well.

wizink, then you must be in the worst category : the ones with broken installations
I don't know how much of the fault is ours, but if canola cleanup didn't helped you
(it actually tries to remove everything canola depends, and them do the apt-get update to fix installation problems)

Can you send me the error? just to see if we have an idea?

Also : what repositories did you have on the device? What device / firmware are you using?

Br

marcelo

Lucky me! So from the top. 2.2007.50-2 running on the N810. If this helps at all, I had canola2 beta5, I believe, installed before I uninstalled it. I noticed that although I had upgraded to the newest version before beta6 was released the same identical message popped up when I tried updating canola-tuning.

As far as what I see in xterm, here you are!

The following packages have unmet dependencies:
canola2: Depends: efl-core (>= 0.9.1.042-maemo2) but it is not going to be installed
Depends: python2.5-efl-core (>= 0.9.1.042-maemo2) but it is not going to be installed
Depends: lightmediascanner0-plugins (>= 0.1.9) but it is not going to be installed
Depends: python2.5-lightmediascanner (>= 0.1.1-maemo7) but it is not going to be installed
Depends: python2.5-dispatcher but it is not going to be installed
Depends: python2.5-dbus-ecore (>= 0.71-1osso9) but it is not installable or
python2.5-edbus (>= 0.1.1-maemo2) but it is not going to be installed
Depends: hildon-imf-ecore (>= 0.1.1) but it is not going to be installed
Depends: python2.5-terra (>= 0.1.4) but it is not going to be installed
Depends: atabake (>= 0.1.3) but it is not going to be installed
Depends: python2.5-downloadmanager (>= 0.2.3) but it is not going to be installed
Depends: canolad (>= 0.1.3-maemo2) but it is not going to be installed
libgnomeprint2.2: Depends: libart-2.0 (>= 2.0.0) but it is not installable

Well, canola tuning should clean this up :/ but seems that your problems is a little worst : / libgnomeprint2.2 we don't need it at all hehehe

Well, so did you managed to install canola clean up after all ? if not :/
I don't know if we can help more :/ and as I use to say we have 2 options

1) to suggest you to flash the device ( this is bad I know )
2) see if you can arrange a fix ip or something on the device, and we will be able to ssh to it, and fix it remotely for you.

Also, take a look at some OLDER threads about removing canola? they tell you how to manually delete all those dependencies, and then you just run apt-get update
to see if helps.

marcelo

I have uninstalled Canola2b6 and installed again the version that has name truncation fixed. This time, it has found all the albums, so that problem must have been related to name truncation. Thanks for fixing it!

As to problems with finger-scrolling, I have found that finger-scrolling works when I slide my finger at the extreme left or the extreme right of the screen. Touching an actual item always appears to open it. Is it possible to widen left/right edges and maybe mark them as scroll areas? One way to mark these areas would be to denote them with "film perforation", as if the user were scrolling through a roll of film.

FMS : this has been widely discussed before.
What I suggest you is to try to keep pressure. touching / softly moving the finger will always be a click (as the first touch is generating a UP event) that represents the click.

So try experimenting with a little more pressure.

click / select only happens if we get a click up event, click up only comes if you touch and then un touch the screen completely (remember this is not a capacitive screen, you need to really press it to detect a click and keep pressing to generate the other events)

Film perforation idea : no ways : / sorry, it's just out of our vision for it ;/

I'm sad that you are having this problems, we will keep studying (not messing the released source) trying to improve this click rate success (for all cases)

Br

Marcelo

My upgrade works great. Just updated from the application manager.

Now for the new themes, youtube and last.fm...

Thanks you guys!

@Wes nice to hear Wish all successful updates wrote here also to see the balance

BR

Marcelo