Kontact Touch 4.8 Packages (conflict free installation)

[Laszlo Papp]

Hey,

> libxcursor comes from our kde-packages the files.kolab.org repository contains
> version 1.10-2 from:
> https://build.pub.meego.com/package/show?package=libxcursor&project=home%3Arzr%3Aharmattan

Yes, that is unknown. The aegis community policy does not apply for
the Community Repository, just for Apps4MeeGo as far as I know. I am
not entirely sure what needs to have that library, but my experience
was that when I ran my application as root from command line. It
worked for me, at least, when I used user (for instance via the
invoker executed from the relevant desktop file entry). It might not
be a universal rule though. Someone needs to investigate why this
library is needed. Many applications do not use it right there in Ovi.

[...]
> Argh so that can be a very nasty problem.
> Laszlo do you have any advice how to fix this in the packaging?

The most appropriate fix is to upgrade to PR 1.2. (SystemSW
implemented the proposed DSME fix), whereas it is not gonna work for
people with older firmwares. Other workarounds are cumbersome and
impractical, but I can mention what comes up to my mind:

1) Do not reboot the device that often (it is related to that by the way).
2) Rename the library or use a "distinguished" path. Set the
LD_PRELOAD when it is really needed accordingly.
3) File a bugreport to put this library into the Nokia SDK or
apps/tools repository, if it is really a central one.

> Should we advise to uninstall the libxcursor package and all
> packages depending on it (kontact-touch) until we figured out a workaround
> for this Meego bug?

The problem is that it can take place with many packages and plugins,
thus what we need to push is a firmware upgrade to everyone as the
best solution. Speaking of compatibility backwards, I would recommend
to investigate each single case what is the most appropriate way of
doing it. As of this issue in question, I would investigate what
exactly uses this library and for that, if I were you. If it is
something common by many application, I would even say, please do feel
free to file a bug report against the public tracker, and I can raise
the issue internally to the SDK team.

> The solution for Qt3D was to get their library into the official repository
> correct?

Nah, it was finally rejected because PR1.2 was too late to get that
integrated, and PR1.3 is not a feature release. They realized firmware
update fixes their problem, so they did not bother further on.

Best Regards,
Laszlo Papp