Problems at use | Problèmes à l'utilisation
Guest, Tuesday 03 November 2009 à 01:41
|
|
|
None of the applets load for cairo-dock. It is apparently testing the version numbers incorrectly.
Errors for all the applets are similar to the following:
warning : (cairo-dock-modules.c:cairo_dock_preload_module_from_directory:376)
this module ('/usr/lib/cairo-dock/libcd-Clipper.so') needs at least Cairo-Dock v1.6.3, but Cairo-Dock is in v2.1.0
It will be ignored
warning : (cairo-dock-modules.c:cairo_dock_preload_module_from_directory:376)
this module ('/usr/lib/cairo-dock/libcd-terminal.so') needs at least Cairo-Dock v2.0.7, but Cairo-Dock is in v2.1.0
It will be ignored
warning : (cairo-dock-modules.c:cairo_dock_preload_module_from_directory:376)
this module ('/usr/lib/cairo-dock/libcd-dnd2share.so') needs at least Cairo-Dock v2.0.7, but Cairo-Dock is in v2.1.0
...
This is on a PPC platform with either Fedora 10 (F10) or F11. Cairo-Dock is version 2.1 on F11. An earlier version of Cairo-Dock had an identical problem in F10. |
matttbe, Tuesday 03 November 2009 à 11:38
|
|
Subscription date : 24 January 2009
Messages : 12573
|
Hello
It seems that you haven't compiled or installed Cairo-Dock Core and its plug-ins with the same version.
Have a look to our wiki for more informations. |
Guest, Tuesday 03 November 2009 à 17:18
|
|
|
Well, I didn't compile myself, cairo-dock was installed via yum/rpm:
cairo-dock.ppc 2.1.0-1.fc11 installed
cairo-dock-devel.ppc 2.1.0-1.fc11 installed
cairo-dock-plug-ins.ppc 2.1.0-1.fc11 installed
Because of the 'at least' phrasing in the error message, I was guessing that the module loading has a standard method for checking for a minimum version number for the core tool and that method was returning an incorrect comparison (i.e. v2.1 should be >= v2.07, or v1.6.3, etc.). Maybe it's an Endian issue? Anyway, I was trying cairo-dock to see what it was like. Since it had the same error on both F10 and F11, I thought I should report it. |
matttbe, Tuesday 03 November 2009 à 18:06
|
|
Subscription date : 24 January 2009
Messages : 12573
|
Yes, this is strange... Do you have this problem after an update ?
@ fabounet: do you know what's the problem ? |
fabounet, Tuesday 03 November 2009 à 18:32
|
|
Subscription date : 30 November 2007
Messages : 17118
|
it would be very amazing that this bug is in the Fedora packages since many months and that noone has noticed it, so I think it may be relative to the "ppc" architecure (few people use it, so I guess packages are not really tested)
the version number of the dock is encoded inside a macro, that is set in the Makefile by automake, and then replaced everywhere in the code.
but the version number of the plug-in is set in the same way, and is correct (it is printed as "%d.%d.%d" in the output, so we can see here that it is correct). The dock version is printed as "%s" so we can't be sure it is correctly read.
the only place we could check it is when the dock checks for a new version. Could you please delete the file ~/.config/cairo-dock/.cairo-dock-last-version, and edit (with sudo) the file /usr/share/cairo-dock/ChangeLog.txt, and change the line
2.1.0 = blablabla
in
0.1.2 = blablabla
if you have a dialog bubble, then we got it. |
Guest, Wednesday 04 November 2009 à 01:46
|
|
|
Okay, quick answer is that it is an endian/ppc issue and a bug in the code (I'm surprised by both).
cairo-dock-modules.c declares:
extern short g_iMajorVersion, g_iMinorVersion, g_iMicroVersion;
cairo-dock.c defines them as:
int g_iMajorVersion, g_iMinorVersion, g_iMicroVersion;
The significant bits where getting lost in translation (heh). Changing 'extern short' to 'extern int' in cairo-dock-modules.c solved the issue.
The longer version is that the earlier suggestion didn't work. I caved, built from source and was able to track it down to the above. It does work much better this way ;).
|
fabounet, Wednesday 04 November 2009 à 13:08
|
|
Subscription date : 30 November 2007
Messages : 17118
|
oh, nicely guessed
I'll fix it immediately, thanks for your help ! |
Problems at use | Problèmes à l'utilisation
|