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 481737 - crash in Deskbar: Searched for "meta"...
crash in Deskbar: Searched for "meta"...
Status: RESOLVED DUPLICATE of bug 474131
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-09-30 01:03 UTC by branstrom
Modified: 2007-09-30 10:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description branstrom 2007-09-30 01:03:30 UTC
What were you doing when the application crashed?
Searched for "meta"...


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.0 2007-09-17 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

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 (436 sec old) ---------------------
create proxy object
create iface
send to iface
Traceback (most recent call last):
  • File "/usr/bin/deluge", line 132 in <module>
    deluge_iface.interactive_add_torrent(filename)
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 63 in __call__
    return self._proxy_method(*args, **keywords)
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 135 in __call__
    **keywords)
  • File "/var/lib/python-support/python2.5/dbus/connection.py", line 603 in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocke
checking for valid crashreport now
checking for valid crashreport now
--------------------------------------------------
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 559, in msg_reply_handler
    reply_handler(*message.get_args_list(**get_args_opts))
  File "/usr/lib/deskbar-applet/modules-2.20-compatible/tracker-module.py", line 417, in <lambda>
    reply_handler = lambda hits: self.recieve_hits(qstring, hits, max),
  File "/usr/lib/deskbar-applet/modules-2.20-compatible/tracker-module.py", line 386, in recieve_hits
    matches.append(TrackerLiveSearchMatch (output))
  File "/usr/lib/deskbar-applet/modules-2.20-compatible/tracker-module.py", line 183, in __init__
    self.add_all_actions (get_actions_for_uri(result['uri']))
  File "/usr/lib/python2.5/site-packages/deskbar/handlers/actions/ActionsFactory.py", line 39, in get_actions_for_uri
    mime = gnomevfs.get_mime_type(uri)
RuntimeError: there was an error reading the file
Comment 1 Sebastian Pölsterl 2007-09-30 10:11:46 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 474131 ***