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 492605 - crash in Deskbar: I had just launched miro...
crash in Deskbar: I had just launched miro...
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-11-02 07:53 UTC by anthony.stellato
Modified: 2007-11-02 14:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description anthony.stellato 2007-11-02 07:53:58 UTC
What were you doing when the application crashed?
I had just launched miro through the deskbar applet.


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: Darklooks
Icon Theme: contrastlarge

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 (15689 sec old) ---------------------
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sDevelopment\sPython' to action group 'ScriptsGroup'
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sDevelopment\sWin32%20(Fedora)' to action group 'ScriptsGroup'
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sDevelopment\sWin32%20(Fedora)' to action group 'ScriptsGroup'
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sBlogging' to action group 'ScriptsGroup'
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sBlogging' to action group 'ScriptsGroup'
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sDebian' to action group 'ScriptsGroup'
(nautilus:5691): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sliable\s.gnome2\snautilus-scripts\sDebian' to action group 'ScriptsGroup'
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):
  • File "/usr/lib/python2.5/site-packages/deskbar/gtkexcepthook.py", line 67 in run
    run_old(*args, **kwargs)
  • File "threading.py", line 440 in run
    self.__target(*self.__args, **self.__kwargs)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/ThreadPool.py", line 67 in _worker
    function(*args, **kwargs)
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/files.py", line 92 in query
    result += self._query_filefolder(query, False)
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/files.py", line 125 in _query_filefolder
    return [FolderMatch(join(prefix, basename(completion)), "file://"+completion, priority=self.get_priority()) for completion in completions]
  • File "/usr/lib/deskbar-applet/modules-2.20-compatible/files.py", line 39 in __init__
    self.add_all_actions( get_actions_for_uri(absname) )
  • 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-11-02 14:30:57 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 ***