gdesklets does not start

Bug #83922 reported by sojourner
228
This bug affects 29 people
Affects Status Importance Assigned to Milestone
gDesklets
Fix Released
Undecided
Unassigned
gdesklets (Debian)
Fix Released
Unknown
gdesklets (Ubuntu)
Triaged
Medium
Unassigned
Declined for Jaunty by Sebastien Bacher
Declined for Lucid by Sebastien Bacher
Declined for Maverick by Sebastien Bacher
Feisty
Won't Fix
Undecided
gDesklets Core Team
Gutsy
Invalid
Medium
Unassigned

Bug Description

Update:
For python2.6 compatibility wish, please see bug #344079

Original description:
Binary package hint: gdesklets

installed gdesklets with synaptic. attempting to start gdesklets gives this error.

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

the .gdesklets dir in /home/~ has this message , no other log messages are generated.

Log messages of /home/ron/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead
gtk.threads_init()

================================================== ========[02/06/07-07:42:13]===
Could not import tiling module!

there are no dmesg or syslog mesages generated

Related branches

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Same problem here

Changed in gdesklets:
status: Unconfirmed → Confirmed
importance: Undecided → Medium
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

I can add that under i386 that's working

Revision history for this message
sojourner (itsmealso2) wrote :

note ! as of febuary 16 ,2007 AM updates the gkdesklets in synaptic is still not working. I uninstalled gdesklets and gdesklets-data using synaptic and complied from source , localy compiled gdesklets connects to the daemon and works , however individual desklets must be downloaded and installed manualy. perhaps you have a bad path or dependency in the x86_64 build farm.

Revision history for this message
Benjamin.M (benjaminm) wrote :

I'm using latest Feisty Fawn, all updates installed. And I have a i386 System, non the less I am experiencing nearly the same problem!
If started from console, I also get the Timeout message. But I have a log which says:

Log messages of /home/ben/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init inst
ead
  gtk.threads_init()

==========================================================[02/22/07-20:24:42]===
=== Unhandled error! Something bad and unexpected happened. ===

[EXC]db type could not be determined
in /usr/lib/gdesklets/gdesklets-daemon: line 127 <module>
in /usr/lib/gdesklets/gdesklets-daemon: line 114 _gdesklets_main
in /usr/lib/gdesklets/utils/ErrorFormatter.py: line 118 _new_imp
in /usr/lib/gdesklets/main/Starter.py: line 2 <module>
in /usr/lib/gdesklets/utils/ErrorFormatter.py: line 118 _new_imp
in /usr/lib/gdesklets/config/DaemonConfigger.py: line 1 <module>
in /usr/lib/gdesklets/utils/ErrorFormatter.py: line 118 _new_imp
in /usr/lib/gdesklets/config/StateSaver.py: line 128 <module>
in /usr/lib/gdesklets/config/StateSaver.py: line 30 __init__
in /usr/lib/gdesklets/config/Backend.py: line 68 Backend
in shelve.py: line 225 open
in shelve.py: line 209 __init__
in anydbm.py: line 80 open
[EXC]/usr/lib/python2.5/anydbm.py

[---] 75 mod = _defaultmod
[---] 76 else:
[---] 77 raise error, "need 'c' or 'n' flag to open new db"
[---] 78 elif result == "":
[---] 79 # db type cannot be determined
[ERR]> 80 raise error, "db type could not be determined"
[---] 81 else:
[---] 82 mod = __import__(result)
[---] 83 return mod.open(file, flag, mode)

Version is 0.35.3-4ubuntu2

I tried dpkg --purge to uninstall it and reinstall it, so its not a config problem I guess.

Revision history for this message
sojourner (itsmealso2) wrote : Re: [Bug 83922] Re: gdesklets does not start feisty herd3 amd64

--- "Benjamin.M" <email address hidden> wrote:

> I'm using latest Feisty Fawn, all updates installed.
> And I have a i386 System, non the less I am
> experiencing nearly the same problem!
> If started from console, I also get the Timeout
> message. But I have a log which says:
>
> Log messages of
> /home/ben/.gdesklets/logs/gdesklets%3A0.0.log
> /usr/lib/gdesklets/main/__init__.py:118:
> GtkDeprecationWarning: gtk.threads_init is
> deprecated, use gtk.gdk.threads_init inst
> ead
> gtk.threads_init()
>
>
==========================================================[02/22/07-20:24:42]===
> === Unhandled error! Something bad and unexpected
> happened. ===
>
> [EXC]db type could not be determined
> in /usr/lib/gdesklets/gdesklets-daemon: line 127
> <module>
> in /usr/lib/gdesklets/gdesklets-daemon: line 114
> _gdesklets_main
> in /usr/lib/gdesklets/utils/ErrorFormatter.py: line
> 118 _new_imp
> in /usr/lib/gdesklets/main/Starter.py: line 2
> <module>
> in /usr/lib/gdesklets/utils/ErrorFormatter.py: line
> 118 _new_imp
> in /usr/lib/gdesklets/config/DaemonConfigger.py:
> line 1 <module>
> in /usr/lib/gdesklets/utils/ErrorFormatter.py: line
> 118 _new_imp
> in /usr/lib/gdesklets/config/StateSaver.py: line 128
> <module>
> in /usr/lib/gdesklets/config/StateSaver.py: line 30
> __init__
> in /usr/lib/gdesklets/config/Backend.py: line 68
> Backend
> in shelve.py: line 225 open
> in shelve.py: line 209 __init__
> in anydbm.py: line 80 open
> [EXC]/usr/lib/python2.5/anydbm.py
>
> [---] 75 mod = _defaultmod
> [---] 76 else:
> [---] 77 raise error, "need 'c' or 'n'
> flag to open new db"
> [---] 78 elif result == "":
> [---] 79 # db type cannot be determined
> [ERR]> 80 raise error, "db type could not
> be determined"
> [---] 81 else:
> [---] 82 mod = __import__(result)
> [---] 83 return mod.open(file, flag, mode)
>
> Version is 0.35.3-4ubuntu2
>
> I tried dpkg --purge to uninstall it and reinstall
> it, so its not a
> config problem I guess.
>
> --
> gdesklets does not start feisty herd3 amd64
> https://launchpad.net/bugs/83922
>
I dont think its exactly the same bug , the i386
version was working with 32bit systems at the time I
filed that bug also I got no meaningful log output.
python id being updated frequently and that may be
causing it , I had a similar problem with freeguide
for a couple of days that was cause by an update to
java.

____________________________________________________________________________________
Have a burning question?
Go to www.Answers.yahoo.com and get answers from real people who know.

Revision history for this message
Jonah (jonah) wrote : Re: gdesklets does not start feisty herd3 amd64

same problem here on feisty amd64... any word on a solution for this yet?

Revision history for this message
sojourner (itsmealso2) wrote :

not a solution but a workaround , pruge gdesklets and gdesklets-data then compile gdesklets from src ( get the src from the gdesklets website) you will probably have to install some extra libs etc to get it to ./configure , once you get it installed (take note of where it installed to its not the same place as the ubuntu pakage) download but do not "install" the gdesklets-data package from the ubuntu repo and unpack it localy and move the desklets to the install dir. this worked on my system your mileage may vary.

Revision history for this message
Jonah (jonah) wrote :

can anyone make a proper deb of this new version so it'll install in correct place etc for now for us all to use while feisty catches up? would be appreciated...

Revision history for this message
Mirzet Kadic (caracal-enl) wrote :

Same problem here too!

Log messages of /home/mk/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead
  gtk.threads_init()

==========================================================[04/10/07-23:08:07]===
Could not import tiling module!

Revision history for this message
Jonah (jonah) wrote :

come on guys, been waiting ages for this to work...

Revision history for this message
Jonah (jonah) wrote :

Log messages of /home/jonah/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead
  gtk.threads_init()

==========================================================[04/25/07-23:11:24]===
Could not import tiling module!

Revision history for this message
Wei-Yee Chan (chanweiyee) wrote :

The same thing happened after I upgraded to Feisty Fawn.

Revision history for this message
SrinivasChavan (srinivas-chavan) wrote :

Please see if my comments posted at following location are of any help.
https://bugs.launchpad.net/ubuntu/+source/gdesklets/+bug/110103

Revision history for this message
hangy (hangy) wrote :

The same problem ("Could not import tiling module!"), rendering gdesklets unusable, still happens in Ubuntu Gutsy Gibbon (amd64).

Revision history for this message
sojourner (itsmealso2) wrote : Re: gdesklets does not start amd64

the work around .deb from Bug #110103 had been working in gutsy until todays (may 21) updates now its back to cannot start daemon.

Revision history for this message
Matt Philmon (mattisking) wrote :

I'm running the "generic" (386) version under Gutsy and see the same problem, more or less. I see all the same stuff about gslice. In my case I have 2 accounts. I don't use gdesklets but the other account does. On my account I can run the daemon just fine since I have no gdesklets to load. I can "Manage" my desklets (bring up the dialogs that list them) but it crashes as soon as I try to add one. On the other account which had two until the other day's updates "broke" it, it can't launch the daemon because it crashes as soon as it tries to load them.

It mentions some mismatch in python...

Here's me starting the daemon (with no desklets defined):
$ gdesklets

***MEMORY-WARNING***: [21699]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
Starting gdesklets-daemon...
Connecting to daemon [ ### ]
***MEMORY-WARNING***: [21701]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
Connected to daemon in 2739 milliseconds.

Once it's running, I can copy the Log with "View Log":
Log messages of /home/mattisking/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is
deprecated, use gtk.gdk.threads_init instead
  gtk.threads_init()
/usr/lib/gdesklets/utils/ErrorFormatter.py:118: RuntimeWarning: Python C API version
mismatch for module tiling: This Python has API version 1013, module tiling has
version 1012.
  module = _old_imp(name, globs, locls, fromlist)
/usr/lib/gdesklets/utils/ErrorFormatter.py:118: RuntimeWarning: Python C API version
mismatch for module x11: This Python has API version 1013, module x11 has version
1012.
  module = _old_imp(name, globs, locls, fromlist)
/usr/lib/gdesklets/utils/ErrorFormatter.py:118: RuntimeWarning: Python C API version
mismatch for module systray: This Python has API version 1013, module systray has
version 1012.
  module = _old_imp(name, globs, locls, fromlist)
/usr/lib/gdesklets/gdesklets-daemon:119: GtkDeprecationWarning: gtk.threads_enter is
deprecated, use gtk.gdk.threads_enter instead
  gtk.threads_enter()

Revision history for this message
Matt Philmon (mattisking) wrote :

I agree with sojourner above and have opened a new bug for Gutsy users of the generic/386 kernel:
https://bugs.launchpad.net/ubuntu/+source/gdesklets/+bug/118718

Revision history for this message
omegazepher (omegazepher) wrote :

Same problem.

Starting gdesklets-daemon...
Cannot establish connection to daemon: timeout!

Log messages of /home/zepher/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead
  gtk.threads_init()

==========================================================[06/09/07-17:49:35]===
Could not import tiling module

Revision history for this message
Shawn vega (svega85-gmail) wrote :

i have the same problem using ubuntu feisty fawn amd64

Revision history for this message
kiryo (kiryo24) wrote :

i found working solution for 64 feisty
workaround deb reposted:

Revision history for this message
Christian Meyer (chrisime) wrote :

The problem should be fixed in bzr. We've been testing it on a amd64 system and the problem no longer occurrs.

Changed in gdesklets:
assignee: nobody → chrisime
status: Confirmed → Fix Committed
Changed in gdesklets:
assignee: nobody → chrisime
status: New → Fix Committed
Revision history for this message
Jeff Ferrari (jeff-oolportal) wrote :

Should this still be happening in gutsy with 0.35.3-4ubuntu2 ? I'm on amd64, fresh install. Getting timeout message and same old error log:

Log messages of /home/jeff/.gdesklets/logs/gdesklets%3A0.0.log
/usr/lib/gdesklets/main/__init__.py:118: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead
  gtk.threads_init()

==========================================================[09/18/07-16:05:36]===
Could not import tiling module!

Revision history for this message
Christian Meyer (chrisime) wrote :

Ubuntu ships a broken version, even in gutsy. DON'T USE IT! We recommend to use a fresh version from bzr. There'll be a beta soon. The final should be ready by the time gutsy being released.

Revision history for this message
sojourner (itsmealso2) wrote :

I downloaded and built the 0.3x branch from bzr on 9/25/07 . I recieve this error trying to run it.

ron@ron-desktop:~$ /usr/local/lib/gdesklets/gdesklets-shell
Connected to daemon in 305 milliseconds.

==========================================================[09/26/07-18:36:21]===
=== Unhandled error! Something bad and unexpected happened. ===

[EXC]
in /usr/local/lib/gdesklets/gdesklets-shell: line 9 <module>
in /usr/local/lib/gdesklets/shell/PluginRegistry.py: line 52 get_plugin
in /usr/local/lib/gdesklets/shell/PluginRegistry.py: line 40 get_plugins_by_pattern
in /usr/local/lib/gdesklets/shell/plugins/Shell/__init__.py: line 70 init
in /usr/local/lib/gdesklets/shell/Plugin.py: line 18 _get_plugins_by_pattern
in /usr/local/lib/gdesklets/shell/PluginRegistry.py: line 40 get_plugins_by_pattern
in /usr/local/lib/gdesklets/shell/plugins/Profiles/__init__.py: line 14 init
in /usr/local/lib/gdesklets/shell/Plugin.py: line 24 _get_plugin
in /usr/local/lib/gdesklets/shell/PluginRegistry.py: line 52 get_plugin
in /usr/local/lib/gdesklets/shell/PluginRegistry.py: line 40 get_plugins_by_pattern
in /usr/local/lib/gdesklets/shell/plugins/gDeskletsClient/__init__.py: line 18 init
in /usr/local/lib/gdesklets/shell/plugins/gDeskletsClient/__init__.py: line 27 __get_daemon
in /usr/local/lib/gdesklets/main/client.py: line 208 set_remove_command
in /usr/local/lib/gdesklets/main/client.py: line 38 __send
in /usr/local/lib/gdesklets/utils/xdr.py: line 75 recv
[EXC]/usr/local/lib/gdesklets/utils/xdr.py

[---] 70 chunk = ""
[---] 71 while (True):
[---] 72 try:
[---] 73 length = ord(s.recv(1))
[---] 74 except:
[ERR]> 75 raise XDRError
[---] 76
[---] 77 if (length): chunk += s.recv(length)
[---] 78
[---] 79 flag = s.recv(1)
[---] 80 if (flag == _CONT): continue
[---] 81

ron@ron-desktop:~$

my system is gutsy ,amd64, up to date

Revision history for this message
sojourner (itsmealso2) wrote :

so where is the beta so we can test it on our systems ? I I've been checking launchpad and gdesklets.de every day.

Revision history for this message
Christian Meyer (chrisime) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

been really busy, hope i can release it within the next days. sorry.

for now, check out a version from bzr. beta will have no or just some minor
modifications.

2007/10/4, sojourner <email address hidden>:
>
> so where is the beta so we can test it on our systems ? I I've been
> checking launchpad and gdesklets.de every day.
>
> --
> gdesklets does not start amd64
> https://bugs.launchpad.net/bugs/83922
> You received this bug notification because you are a bug assignee.
>

--
Christian Meyer
GNOME: http://www.gnome.org
gDesklets: http://www.gdesklets.org
AIM: chrisime
ICQ: 72107443
Jabber: <email address hidden>
MSN: <email address hidden>
Skype: chrisime77
Yahoo: <email address hidden>

Revision history for this message
sojourner (itsmealso2) wrote : Re: gdesklets does not start amd64

see my comment above , I did check out and build the 0.3x branch on 9/25 with the posted results , it built with no errors but wouldnt run . I'll try again tonight.

Revision history for this message
Christian Meyer (chrisime) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

I tried it on a amd64 and it worked nicely. Are you using a 32bit ubuntu or
a 64bit ubuntu?

Revision history for this message
sojourner (itsmealso2) wrote : Re: gdesklets does not start amd64

64bit, I havent used 32bit since the athalon64 first came out several years ago. I saw your post in a dupe of this bug and the problem may be that I didn't get all of the libs wiped out before I built the version from bzr , I have tried several different .debs and also built several versions from source and some of them put their files in different places , I will hunt them down and clean them all out by hand ( not just using make uninstall) and try again tonight and report.

Revision history for this message
sojourner (itsmealso2) wrote :

oh and additional info , the version of gdesklets shipped with fedora fc8 alpha (64bit) works fine although I did have to move the desklets themselves over from gutsy because fedora only includes 2 desklets.

Revision history for this message
Christian Meyer (chrisime) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

It'd be interesting, what fedora did to get it working. could you somehow
show me the diff?
that'd be great!

Revision history for this message
sojourner (itsmealso2) wrote : Re: gdesklets does not start amd64

I have no idea what the difference is , I'm sending you the fedora RPM for you to examine.

Revision history for this message
sojourner (itsmealso2) wrote :

ok I ruthlessly exterminated every trace of any previous install of gdesklets . I checked out a new copy of 0.3x from "https://code.launchpad.net/gdesklets" . I ran ./autogen.sh , make , sudo make install . I did not see any errors in any step , I copied the output of the terminal for each step and saved it to a file so I have logs of the build and install . when I try to run it I get.

ron@ron-desktop:~$ /usr/local/lib/gdesklets/gdesklets
Starting gdesklets-daemon...
Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:21]===
Registering new control "/usr/local/lib/gdesklets/Controls/ArrayBuffer".

Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:21]===
Registering new control "/usr/local/lib/gdesklets/Controls/Time".

Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:21]===
Registering new control "/usr/local/lib/gdesklets/Controls/Sensors".

Connecting to daemon [ ###]
==========================================================[10/04/07-21:30:21]===
Registering new control "/usr/local/lib/gdesklets/Controls/URI".

Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:21]===
Registering new control "/usr/local/lib/gdesklets/Controls/EventPipe".

Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:22]===
Registering new control "/usr/local/lib/gdesklets/Controls/System".

Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:22]===
Registering new control "/usr/local/lib/gdesklets/Controls/Calendar".

Connecting to daemon [ ### ]
==========================================================[10/04/07-21:30:22]===
Registering new control "/usr/local/lib/gdesklets/Controls/HDDTemp".

Connected to daemon in 1624 milliseconds.

==========================================================[10/04/07-21:30:22]===
=== Unhandled error! Something bad and unexpected happened. ===

[EXC]
in /usr/local/lib/gdesklets/gdesklets: line 393 <module>
in /usr/local/lib/gdesklets/gdesklets: line 268 parse_command
in /usr/local/lib/gdesklets/gdesklets: line 177 __open_profile
in /usr/local/lib/gdesklets/gdesklets: line 167 __client_daemon
in /usr/local/lib/gdesklets/main/client.py: line 208 set_remove_command
in /usr/local/lib/gdesklets/main/client.py: line 38 __send
in /usr/local/lib/gdesklets/utils/xdr.py: line 75 recv
[EXC]/usr/local/lib/gdesklets/utils/xdr.py

[---] 70 chunk = ""
[---] 71 while (True):
[---] 72 try:
[---] 73 length = ord(s.recv(1))
[---] 74 except:
[ERR]> 75 raise XDRError
[---] 76
[---] 77 if (length): chunk += s.recv(length)
[---] 78
[---] 79 flag = s.recv(1)
[---] 80 if (flag == _CONT): continue
[---] 81

ron@ron-desktop:~$

Revision history for this message
sojourner (itsmealso2) wrote :

just for grins I'm going to uninstall the just built gdesklets and see what happens if I unpack the fedora rpm and copy it into the respective directories , worst I can do is trash my system.

Revision history for this message
sojourner (itsmealso2) wrote :

well as I said I would try above I unpacked the fedora RPM ( I did that in fedora , ubntu archive manager didnt speak rpm) and copied the fedora /usr/lib64/gdesklets to ubuntu /usr/lib64/gdesklets and the fedora /usr/share/gdesklets to ubuntu /usr/share/gdesklets also the mime ,pixmaps and aplications entrys to the respective ubuntu dirs and ran /usr/lib64/gdesklets/gdesklets in a terminal and miricle of miricles it runs :) . had to copy the controls etc i had kept from ubuntu's deb into /usr/share/gdesklets since the fedora version didnt have any there but its working and nothing is smoking yet.

Revision history for this message
sojourner (itsmealso2) wrote :

heres a screenshot

Revision history for this message
Christian Meyer (chrisime) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

good idea, I'll check the rpm in the meantime.

Revision history for this message
jcarminati (jcarminati) wrote : Re: gdesklets does not start amd64

Just to report that since a couple of days I'm having exactly the same error as the one described by sojourner on comment #24.
Hope to find this problem solved soon.

Revision history for this message
Christian Meyer (chrisime) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

Could you also try the rpm version?

Revision history for this message
Wei-Yee Chan (chanweiyee) wrote : Re: gdesklets does not start amd64

Version 0.35.3 works fine on Ubuntu Gutsy Gibbon now:

http://chanweiyee.blogspot.com/2007/10/upgraded-to-ubuntu-710-gutsy-gibbon.html

tolaware (tola-ware)
Changed in gdesklets:
status: Fix Committed → Confirmed
Changed in gdesklets:
assignee: chrisime → gdesklets-core-team
status: Fix Committed → In Progress
status: Fix Committed → In Progress
assignee: chrisime → gdesklets-core-team
status: Confirmed → In Progress
assignee: chrisime → gdesklets-core-team
39 comments hidden view all 119 comments
Revision history for this message
LumpyCustard (orangelumpycustard) wrote :

Please close for Feisty as Won't Fix? This goes for all the other Feisty bugs.

Revision history for this message
Hew (hew) wrote :

Ubuntu Feisty Fawn is no longer supported, so a SRU will not be issued for this release. Marking Feisty as Won't Fix.

Changed in gdesklets:
status: In Progress → Won't Fix
Revision history for this message
Savvas Radevic (medigeek) wrote :

I believe this exists in Ubuntu 9.04 Jaunty alpha 5 as well (tried to rebuild and run the deb source package)

Revision history for this message
Savvas Radevic (medigeek) wrote :

https://bugs.edge.launchpad.net/ubuntu/+source/gdesklets/+bug/83922
https://bugs.edge.launchpad.net/ubuntu/+source/gdesklets/+bug/336200

I tried searching on Google and stumbled upon an archlinux bug, someone mentioned the new version fixes it:
http://bugs.archlinux.org/task/12217
"Hi, problem is indeed solved in gdesklets-0.36.1! Thanks very much."

http://archive.gdesklets.info/whatsnew/0.36.1/

I tried the new debian version and it doesn't work unfortunately:
$ gdesklets check
Checking requirements:
 - sys ... found
 - xml.parsers.expat ... found
 - xml.sax ... found
 - gtk ... found
**
ERROR:/build/buildd/pyorbit-2.24.0/src/pyorbit-utils.c:39:_pyorbit_escape_name: assertion failed: (keyword_mod != NULL)
 - ORBit ...Aborted (core dumped)

I also tried the debian version of python-pyorbit, and it failed with the same message again:
$ gdesklets restart
Restarting gdesklets-daemon...
Starting gdesklets-daemon...
Connecting to daemon [ ### ]
==========================================================[03/11/09-17:55:48]===
Could not import tiling module!
Cannot establish connection to daemon: timeout!
The log file might help you solving the problem.

$ gdesklets shell
forger@ubuntu:~$ _new_imp() takes at most 4 arguments (5 given)
EventPipe in /usr/lib/gdesklets/Controls/EventPipe is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
Calendar in /usr/lib/gdesklets/Controls/Calendar is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
Time in /usr/lib/gdesklets/Controls/Time is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
System in /usr/lib/gdesklets/Controls/System is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
HDDTemp in /usr/lib/gdesklets/Controls/HDDTemp is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
Sensors in /usr/lib/gdesklets/Controls/Sensors is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
ArrayBuffer in /usr/lib/gdesklets/Controls/ArrayBuffer is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
URI in /usr/lib/gdesklets/Controls/URI is NOT a valid plugin!
_new_imp() takes at most 4 arguments (5 given)
Random in /usr/lib/gdesklets/Controls/Random is NOT a valid plugin!

==========================================================[03/11/09-17:56:15]===
Could not import tiling module!

Revision history for this message
Hew (hew) wrote :

If someone can verify the fix in 0.36.1, it would be worth getting a Debian sync for Jaunty (FFe required).

Revision history for this message
Savvas Radevic (medigeek) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

> If someone can verify the fix in 0.36.1, it would be worth getting a
> Debian sync for Jaunty (FFe required).

Unfortunately, it doesn't. I get the same errors when trying these test cases:
1) Debian 's current package gdesklets and python-pyorbit and python-pyorbit-omg
2) Debian 's current package gdesklets and Ubuntu's python-pyorbit and
python-pyorbit-omg
3) Ubuntu 's current package gdesklets and Debian's python-pyorbit and
python-pyorbit-omg

I use ubuntu 64-bit/amd64 jaunty alpha 5
Your mileage may vary of course. :)

Revision history for this message
Savvas Radevic (medigeek) wrote : Re: gdesklets does not start amd64

Can anyone with 32-bit Ubuntu 8.04, 8.10 or 9.04 confirm that gdesklets works as expected on 32-bit Ubuntu?

Revision history for this message
Ronnie Redd (cruzit) wrote : Re: [Bug 83922] Re: gdesklets does not start amd64

On Thursday 12 March 2009 16:39:08 Savvas Radevic wrote:
> Can anyone with 32-bit Ubuntu 8.04, 8.10 or 9.04 confirm that gdesklets
> works as expected on 32-bit Ubuntu?
>
32 bit works fine on 8.04 and 8.10 here.
--
Thank You,
Ronnie Redd

Fingerprint:
7B9430791CE3066D944D1C8CB0A22F3A1B4998F0

Revision history for this message
Savvas Radevic (medigeek) wrote : Re: gdesklets does not start amd64

It seems that gdesklets requires packages from python2.4:
http://ubuntuforums.org/showthread.php?t=582721

Revision history for this message
Savvas Radevic (medigeek) wrote :

Woa!

I changed /usr/lib/gdesklets/gdesklets python -> python2.5
$ head /usr/lib/gdesklets/gdesklets
#! /usr/bin/env python2.5

$ gdesklets check
Checking requirements:
 - sys ... found
 - xml.parsers.expat ... found
 - xml.sax ... found
 - gtk ... found
 - ORBit ... found
 - bonobo.ui ... found
Requirements checking done. Your system looks ok!

Revision history for this message
Savvas Radevic (medigeek) wrote :

Attached a debdiff patch, I've restricted the python version to 2.5 and fixed interpreters (using sed, in debian/rules).

Revision history for this message
Savvas Radevic (medigeek) wrote :

build log for the patch above

Revision history for this message
Savvas Radevic (medigeek) wrote :

A small change after consulting #ubuntu-motu folks, package version 0.36-5build1ubuntu1 -> 0.36-5ubuntu1. I've attached the new patch (the rest is the same!) :)

I forgot to mention that I've tested the patch on my amd64 jaunty and it works as expected!

Revision history for this message
Johan Ryberg (jryberg) wrote :

Same problem in 9.04 x86, attached error message as "error.txt"

jory01@jory01-ubuntu:~$ uname -a
Linux jory01-ubuntu 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:23 UTC 2009 i686 GNU/Linux

jory01@jory01-ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

Revision history for this message
Savvas Radevic (medigeek) wrote :

Gutsy will soon reach end-of-life, it's best to ask for a jaunty fix

Changed in gdesklets (Ubuntu Gutsy):
assignee: gdesklets-core-team → nobody
status: In Progress → Invalid
Changed in gdesklets (Ubuntu):
assignee: gdesklets-core-team → nobody
status: In Progress → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Uploaded. Sitting in the queue.

Changed in gdesklets (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gdesklets - 0.36-5ubuntu1

---------------
gdesklets (0.36-5ubuntu1) jaunty; urgency=low

  * Not compatible with python 2.6 (LP: #83922)
  * debian/control, debian/control.in:
    + Depends: python-all-dev
    + XS-Python-Version: << 2.6
  * debian/rules: Fix interpreter python -> python2.5

 -- Savvas Radevic <email address hidden> Fri, 13 Mar 2009 11:08:34 +0100

Changed in gdesklets:
status: Fix Committed → Fix Released
Changed in gdesklets:
status: New → Invalid
description: updated
Revision history for this message
meral (meral) wrote :

This problem is NOT solved in Lucid Lynx (10.0.4). It appears exactly as described.

Revision history for this message
bc90021 (f-launchpad-bc90021-net) wrote :

I am also seeing this problem on Lucid Lynx (10.04). Starting "gdesklets" gives me:

Starting gdesklets-daemon...
Connecting to daemon [### ]
=========================================[date and time]=====
Could not import tiling module!

Connecting to daemon [ ### ]
Cannt establish connection to daemon: timeout!
The log file might help you solving the problem.

Of course, there is nothing in the directory ~/.gdesklets/logs...

Revision history for this message
Bjoern Koch (h.humpel) wrote :

Just a quick note for the "Could not import tiling module!" error.

This error occurs (AFAIK) when there are some links missing.
When compiling from source, you will have to do the following in your gDesklets source directory:

cd utils
ln -s .libs/*.so .
cd ../libdesklets/system
ln -s .libs/*.so .

Again, this fixes things (here) when compiling from source.
I don't know what you will have to do where to have it fixed in ubuntu etc., but I guess this shouldn't be too hard to figure out.

Hope that helps.

Revision history for this message
Kim HyunKang (kimhyunkang) wrote :

I'm seeing exactly the same message in Lucid Lynx(10.04), which is a fresh install.

tags: added: lucid
Revision history for this message
pioruns (pioruns) wrote :

Same in Lucid Lynx AMD64, gdesklets 0.36.1-4
In attachment I included command line output.

Revision history for this message
tassini (tassini) wrote :

It does not work at all in Lucid 32 nor 64.

Revision history for this message
Matt Thomason (mthomason) wrote :

Still broken ("Could not import tiling module!" error) in Maverick

summary: - gdesklets does not start amd64
+ gdesklets does not start
tags: added: maverick
removed: amd64
Revision history for this message
Matt Thomason (mthomason) wrote :

Quick note in case anyone queries why I edited the title+tags (although its fairly obvious) - this is broken in both 32 and 64

Changed in gdesklets (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Mark Duncan (eattheapple) wrote :

After all these years, this broken package is *still* in the repository? Judging by the almost complete lack of developer interest in this bug, I'd consider it abandoned and the package should just be removed.

Revision history for this message
Joe Sapp (sappj) wrote :

At least 3 active gDesklets developers have commented on this bug during its lifetime, so you must mean Ubuntu developers. It might be useful for someone to create a PPA of the latest version (http://launchpad.net/gdesklets/0.3x/release-of-0.36.2/+download/gDesklets-0.36.2.tar.bz2)

Revision history for this message
Amedee Van Gasse (amedee) wrote :

Bug confirmed for Ubuntu 10.04 Lucid Lynx on amd64

Revision history for this message
tai.oak (xxxjunkxxx) wrote :

Also confirmed for Ubuntu 10.04 LTS - the Lucid Lynx on x64
==
gdesklets
Starting gdesklets-daemon...
Connecting to daemon [ ### ]
==========================================================[08/01/10-01:43:41]===
Could not import tiling module!

Cannot establish connection to daemon: timeout!
The log file might help you solving the problem.

Revision history for this message
curran_kelleher (curran-kelleher) wrote :

Confirmed in 10.04. ~/.gdesklets/logs directory is empty. I can't believe this 3-year-old bug has not yet been fixed.

Revision history for this message
Casper (casper-ravenhorst) wrote :
Revision history for this message
Stefan Brozinski (stefan-brozinski) wrote :

I can confirm that the fix proposed in Casper's link works (Lucid, amd64). The original location is here:

  http://forums.opensuse.org/english/get-help-here/applications/409465-fix-gdesklets.html

Revision history for this message
Roger Walser (rwalser) wrote :

I also can confirm that the fix proposed ind posting #111 works. My system, Notebook Acer Aspire 5520 amd 64, Ubuntu 10.04

Aiman Baharna (aiman)
Changed in lucid:
status: New → Invalid
Revision history for this message
Bjoern Koch (h.humpel) wrote :

curran_kelleher wrote on 2010-08-25:
> I can't believe this 3-year-old bug has not yet been fixed.

Well, we (the gdesklets team) can't believe it either.
We have released a fix a looong time ago (August 2007, see post #21).
Ubuntu is still stuck on 0.36.1 even though we have released 0.36.2 in February 2010.
There is not much we can do about it if there is nobody willing or able to build a new ubuntu package of gDesklets as right now it looks like all (active) member of the gdesklets team are running non-ubuntu linux systems.

Finally, take a look at post #23 (September 2007, but still up-to-date :/ ):
"Ubuntu ships a broken version, even in gutsy. DON'T USE IT! We recommend to use a fresh version from bzr."

I would recomment to use the latest source package instead (at the moment this is 0.36.2 which can be found here: http://www.gdesklets.info/archive/gDesklets/ ) as the bzr version is a development version.

Same for the gdesklets-data package. This is packed with lots of *very* old and non-working desklets. We have been complaining about it for a looong time, too. But it is still out there giving users a hard time.
So again: DON'T USE IT!

I know this is not helping, but I feel it needs to be said what is going wrong here (and why).
We would be more than happy if there was a working or better (or any ?) gDesklets support in ubuntu. We would be more than happy to find someone to set up a PPA...

Just my 5 cents ;).

Greetings, Bjoern

Revision history for this message
llwynrt (marie-lyse-briffaud) wrote :

I take rpm package here : http://rpm.pbone.net/index.php3/stat/4/idpl/14471995/dir/pclinuxos/com/gdesklets-0.36.2-1pclos2010.i586.rpm.html
and convert with alien.
it's work on ubuntu 10.10 64bits

Hew (hew)
Changed in gdesklets:
status: Invalid → Fix Released
Changed in gdesklets (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Hew (hew) wrote :

Reported new upstream version to Debian.

Changed in gdesklets (Debian):
status: Unknown → New
Aiman Baharna (aiman)
affects: lucid → malone
Revision history for this message
pioruns (pioruns) wrote :

It's affecting me right now.
Linux pioruns-machine 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux
python2.6 - 2.6.6-5ubuntu1
gdesklets - 0.36.1-4
Logs from installing, gdesklets check and gdesklets run in attachment.

Revision history for this message
Joe Sapp (sappj) wrote :

Please try 0.36.3. If you don't want to compile from source, please bug the Ubuntu devs or someone who can create a PPA.

Micah Gersten (micahg)
affects: launchpad → null
Revision history for this message
Bachi (m-bachmann) wrote :

Can't get it to run from the Ubuntu packages (same as mentioned above). Someone should update the PPA to use 0.36.3.

Curtis Hovey (sinzui)
no longer affects: null
Revision history for this message
boucek (boucek) wrote : I can't believe you helped me save over $1,000 on this watches

Hello Customer

Don't hesitate. We do our best to satisfy our customers and ensure fast delivery and excellent service. If you receive a damaged watch we will ship another one to you free of charge.
Make your order before the prices go up.

**************************************************************************************
Today I received my two watches. Both watches were spectacular, you guys did a wonderful job and I will definitely recommend you to all my friends!
Thankee!
                     Marla Friedman
**************************************************************************************

Click here ---> http://ranoa.ru

Changed in gdesklets (Debian):
status: New → Fix Released
Displaying first 40 and last 40 comments. View all 119 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.