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 488115 - crash in Deskbar: typing "www.google.com" ...
crash in Deskbar: typing "www.google.com" ...
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-10-19 01:57 UTC by nibblesmx
Modified: 2007-10-19 02:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description nibblesmx 2007-10-19 01:57:31 UTC 
What were you doing when the application crashed?
typing "www.google.com" into deskbar...



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

System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
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 (411 sec old) ---------------------
(tilda:7190): Gdk-CRITICAL **: gdk_window_set_geometry_hints: assertion `GDK_IS_WINDOW (window)' failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00017 (tilda)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
/usr/lib/python2.5/site-packages/GDebi/GDebi.py:93: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed
  self.window_main.set_sensitive(False)
/usr/lib/python2.5/site-packages/GDebi/GDebi.py:93: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed
  self.window_main.set_sensitive(False)
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSERROR: execution of prepared query UpdateFileMove failed due to constraint failed with return code 19
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x320015d specified for 0x3200359 (Shutting d).
ERROR: excessive busy count in query UpdateFile and thread (null)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00017 (tilda)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Traceback (most recent call last):

+ Trace 171299

  • 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 433 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 402 in recieve_hits 
    matches.append(TrackerLiveSearchMatch (output))
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/tracker-module.py", line 191 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


Christoph Wolk





          2007-10-19 02:42:50 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 ***