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 488440 - crash in Deskbar: buscando monitor del sis...
crash in Deskbar: buscando monitor del sis...
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 22:09 UTC by luisasolarf
Modified: 2007-10-19 22:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description luisasolarf 2007-10-19 22:09:16 UTC 
What were you doing when the application crashed?
buscando monitor del sistema


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: 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 (317 sec old) ---------------------
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-notify.c:3Throttle level is 0
Advertencia del gestor de ventanas: last_user_time (134641248) is greater than comparison timestamp (3124346656).  This most likely represents a buggy client sending inaccurate timestamps in messages 
Advertencia del gestor de ventanas: 0xa00029 (Panel late) appears to be one of the offending windows with a timestamp of 134641248.  Working around...
** (gnome-app-install:6481): WARNING **: return value of custom widget handler was not a GtkWidget
/usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1261: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed
  item.applications.set_default_sort_func(None)
changed extensions
** (gnome-app-install:6801): WARNING **: return value of custom widget handler was not a GtkWidget
/usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1261: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed
  item.applications.set_default_sort_func(None)
Advertencia del gestor de ventanas: La ventana 0x3e02b48 () ha establecido la propiedad MWM indicando que no es redimensionable, pero configuró el tamaño mínimo a 456 x 278 y el tamaño máximo a 2
Advertencia del gestor de ventanas: La ventana 0x3e02b48 () ha establecido la propiedad MWM indicando que no es redimensionable, pero configuró el tamaño mínimo a 456 x 278 y el tamaño máximo a 2
--------------------------------------------------
Traceback (most recent call last):

+ Trace 171550

  • 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 22:30:59 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 ***