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 402500 - Error executing program
Error executing program
Status: RESOLVED FIXED
Product: deskbar-applet
Classification: Deprecated
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
: 407102 414321 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-30 16:50 UTC by su610
Modified: 2009-05-01 18:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description su610 2007-01-30 16:50:12 UTC 
What were you doing when the application crashed?
Scoregge varie .Ah ora ricordo mi grattavo il naso..


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

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

Traceback (most recent call last):

+ Trace 106577

  • File "/usr/lib/python2.4/site-packages/deskbar/DeskbarApplet.py", line 121 in on_match_selected 
    match.action(text)
  • File "/usr/lib/deskbar-applet/handlers/programs.py", line 76 in action 
    self._desktop.launch([])
GError: Esecuzione del processo figlio "gtkpod" (No such file or directory) fallita 






Comment 1


Damien Durand





          2007-02-12 17:14:17 UTC
        



*** Bug 407102 has been marked as a duplicate of this bug. ***






Comment 2


Daniel Holbach





          2007-02-12 19:08:01 UTC
        



Hum... why was this marked OBSOLETE? We have https://launchpad.net/ubuntu/+source/deskbar-applet/+bug/66353 still open.






Comment 3


Sebastian Pölsterl





          2007-09-18 09:27:52 UTC
        



*** Bug 414321 has been marked as a duplicate of this bug. ***






Comment 4


Sebastian Pölsterl





          2009-05-01 18:48:25 UTC
        



This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.