After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 436921 - crash in Deskbar: Tomboy doesn't work so n...
crash in Deskbar: Tomboy doesn't work so n...
Status: RESOLVED DUPLICATE of bug 403752
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-05-08 15:37 UTC by apreche
Modified: 2007-05-08 19:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description apreche 2007-05-08 15:37:19 UTC
What were you doing when the application crashed?
Tomboy doesn't work so nicely with Xfce. It locked up on logout.


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Blubuntu
Icon Theme: Tango

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors ---------------------
Watching directory /home/apreche/Projects/games/orbit/seeker (total watches = 33)
[DEBUG]: Tomboy remote control active.
Watching directory /home/apreche/Projects/games/orbit/orbiter (total watches = 34)
Watching directory /home/apreche/Projects/myfeed/magpierss/extlib (total watches = 35)
Watching directory /home/apreche/Projects/fief/magpierss/scripts/smarty_plugin (total watches = 36)
Watching directory /home/apreche/Projects/fief/magpierss/scripts/templates (total watches = 37)
Watching directory /home/apreche/Projects/games/defense/trunk/classes (total watches = 38)
[DEBUG]: EnableDisable Called: enabling... True
[DEBUG]: Binding key '<Alt>F12' for '/apps/tomboy/global_keybindings/show_note_menu'
[DEBUG]: Binding key '<Alt>F11' for '/apps/tomboy/global_keybindings/open_start_here'
(Tomboy:10251): libtomboy-WARNING **: Binding '<Alt>F11' failed!
starting indexing...
indexing #1 - /home/apreche/Desktop
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 157 in load_all
    self.load (f)
  • File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 139 in load
    mod_instance = getattr (mod, handler) ()
  • File "/usr/lib/deskbar-applet/handlers/tracker-handler.py", line 201 in __init__
    self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
  • File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 410 in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 230 in __init__
    _dbus_bindings.UInt32(0))
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 169 in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/trackerd exited with status 0

Comment 1 apreche 2007-05-08 15:53:00 UTC
Never mind. I thought this was a Tomboy crash. I'm trying to switch to Xfce. Tomboy basically j ust doesn't work at all. It runs for a bit, then eventually takes over 100% of the CPU. This makes it impossible to logout. Meanwhile, I'm also using Deskbar through XfApplet. It works fine. When I logout and log back in, Deskbar IS remembered by the Xfce session. However, the session is unable to start it properly. I have to kill deskbar and start it again by re-adding the applet to the panel in order for it to work. 
Comment 2 Susana 2007-05-08 19:35:18 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 403752 ***