This is likely related to KDE bug #182869 which itself implies it to be
a Qt issue fixable by setting the environment variable QT_NO_GLIB to 1.
KDE bug is here: https://bugs.kde.org/show_bug.cgi?id=182869
** Bug watch added: KDE Bug Tracking System #182869
Just ran into this problem in Jaunty when testing smem (mentioned on
this weeks LWN front page), and also described in the smem list archive
here by someone else:
http://selenic.com/pipermail/smem/2009-April/14.html
Apparently the Debian package does have python-tk as a requirement, as
can be
Just to confirm that dropping the -k option for modprobe fixes this for
me too with Jaunty on AMD64.
I'd just tracked it down and found that Ralph saved me the bother of
reporting it. ;-)
--
[jaunty] microcode.ko not loaded due to incorrect modprobe call
https://bugs.launchpad.net/bugs/346265
Instead of adding a symlink I created a file called
/etc/ld.so.conf.d/java.conf which contained :
/usr/lib/jvm/java-6-sun-1.6.0.13/jre/lib/amd64/server/
That was enough to get the library resolved.
Should it be the Java packages fixing this ? I would have thought that
they would be using the
