gDesklets on AMD64 Feisty will not start/work

and if i run from terminal i get this:

jonah@jonah-desktop:~$ gdesklets
Starting gdesklets-daemon...
Cannot establish connection to daemon: timeout!
The log file might help you solving the problem.
jonah@jonah-desktop:~$

confirmed here. fresh feisty install after the official release, AMD64.

It also happened to me just after I had rebooted after Feitsty update, and I'm running the AMD64 distro, as winzo

Well it seems that it works when it's compiled from the source, but I had to add --disable-dependency-tracking to ./confgure to avoid the script to tell me that he couldn't find libraries I had installed nonetheless.

Confirmed again. If it works from the source, maybe someone could build a new .deb for now. Is there a way to find out who built the original? (Not that I'm blaming anyone, I'm just assuming that they would know how to make a new .deb) Maybe its as simple as updating the version, assuming that Dizzi used the latest version.

Same problem here. AMD64 Feisty -> gdesklets doesn't work.
Log last line: Could not import tiling module!

I've used the latest version of gDesklets (0.35.4), but as I said I had to disable dependency-tracking. Couldn't it be a problem to publish a .deb without dependency management (I don't know how to make it but I could try to learn if it's not too hard).

I no longer work on gDesklets.

It would be best to report this bug upstream on GNOME's bugzilla.

AFAIR, tiling is a C python module, so if it doesn't import properly, it's probably because it wasn't compiled properly. You should check the build log. Maybe it's a matter of PIC/pic. It doesn't look like a packaging issue.

This is already reported there http://bugzilla.gnome.org/show_bug.cgi?id=434397

In fact I'm aware that it will not resolve the problem, but I don't have the skills for this, so I just publish a package that works at home on a Feisty Fawn with amd64:
If you need other versions, I haven't tried but just post and I'll see what I can do.

The package is in attachment.

Dizzi's package works for me. (thanks, Dizzi)

this deb also worked for me but with a major problem side-affect, it's wiped all my default file associations out completely so now nothing opens with anything: http://ubuntuforums.org/showthread.php?p=2599591

    Well, I'm arriving after the battle (french expression) so I just
post the answer found on ubuntuforums.org: "reinstall the packages
gnome-mime-data, shared-mime-info, and mime-support using synaptic" (thx
ComplexNumber).

    That's fun because I had the same problem without being able to
guess that it was due to my own package. Now if anybody knows why it has
done this, please tell me.

Following work around working fine for me, without affecting file associations:
- Installed gdesklet and gdesklet-data using synaptic
- Downloaded Dizzi's package
- Extracted 'lib' folder from the package
- Copied it onto /usr/lib/
- Tried 'gdesklet start'. Worked fine.

So get the maintainer fix the build

Is Benoît having a bad week or is he this way naturally?

I mean the solution to this bug is not to exchange some brown-paper package. The build log needs to be checked, and the packages to be compared.

Yes, indeed, this bug seems just a packaging/compiling bug, but can give users quite a headache. I was also experimenting this same problem, downloaded the deb posted above but instead of installing followed this user tip:

http://ubuntuforums.org/showpost.php?p=2601673&postcount=14

I can confirm this bug on Feisty, amd64.

This bug still seems to be present in gutsy 64bit too :(

Confirmed this doesn't work on Gutsy 64bit as well. I got 2 things when on the console. But can't find anything in the logs.

trmentry@kashyyyk:~$ gdesklets
Starting gdesklets-daemon...
Cannot establish connection to daemon: timeout!
The log file might help you solving the problem.

I can't find anything in my logs that would be of use.

It's been almost a year and yet this bug still exists. This package should NOT be listed under "Add/Remove Programs" if it doesn't work (I just tried it today; still broken). If there are no plans to fix it (as seems to be the case) and no one wants to step up to the plate to properly maintain this package then it just needs to be removed to avoid any future confusion.

It's not gdesklets' fault, if you believe it or now. Try to make sure,
python2.4 is used instead of python2.5.
This should fix the problem. Python 2.5 on <hardy seem not to work. I don't
remember which version of python is used in feisty. Anyway, feisty is almost
one year old now and you should upgrade to gutsy or hardy.

It's been working for me since I upgraded to Gutsy Gibbon.

https://bugs.launchpad.net/ubuntu/+source/gdesklets/+bug/83922/comments/59