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 454178 - crash in Deskbar: I just opened a YouTube ...
crash in Deskbar: I just opened a YouTube ...
Status: RESOLVED DUPLICATE of bug 403752
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-07-06 07:05 UTC by tomás pollak
Modified: 2007-07-07 21:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description tomás pollak 2007-07-06 07:05:33 UTC 
What were you doing when the application crashed?
I just opened a YouTube video using the Gnash Shockwave Plugin for Firefox, in my Ubuntu Macbook AMD64 Gutsy Tribe 2 install. I was hoping that Gnash could actually replace the propietary Flash (specially since there's no native 64 bit version), but it seems it ain't ready yet!


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.4 2007-06-29 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-7-generic #1 SMP Mon Jun 25 17:07:55 GMT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tangerine

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 ---------------------
Initialising tracker...
***MEMORY-WARNING***: trackerd[29738]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this progr
** (trackerd:29738): WARNING **: Tracker daemon is already running - exiting
** Message: Not starting remote desktop server
** (gnome-cups-icon:29743): WARNING **: IPP request failed with status 1280
** (gnome-cups-icon:29743): WARNING **: IPP request failed with status 1280
(gnome-panel:29682): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24
  PID TTY          TIME CMD
***MEMORY-WARNING***: gnome-terminal[29843]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this
--------------------------------------------------
Traceback (most recent call last):

+ Trace 146052

  • File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 149 in load_all 
    self.load (f)
  • File "/usr/lib/python2.5/site-packages/deskbar/ModuleLoader.py", line 131 in load 
    mod_instance = getattr (mod, handler) ()
  • File "/usr/lib/deskbar-applet/handlers/tracker-handler.py", line 201 in __init__ 
    self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
  • File "/var/lib/python-support/python2.5/dbus/bus.py", line 240 in get_object 
    follow_name_owner_changes=follow_name_owner_changes)
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 236 in __init__ 
    self._named_service = conn.activate_name_owner(bus_name)
  • File "/var/lib/python-support/python2.5/dbus/bus.py", line 179 in activate_name_owner 
    self.start_service_by_name(bus_name)
  • File "/var/lib/python-support/python2.5/dbus/bus.py", line 277 in start_service_by_name 
    'su', (bus_name, flags)))
  • File "/var/lib/python-support/python2.5/dbus/connection.py", line 603 in call_blocking 
    message, timeout)
DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/trackerd exited with status 0 






Comment 1


palfrey





          2007-07-07 21:18:42 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 403752 ***