GNOME Bugzilla – Bug 550465
crash in Deskbar: adding deskbar to the pa...
Last modified: 2008-09-02 16:21:14 UTC
What were you doing when the application crashed? adding deskbar to the panel Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.23.90 2008-08-18 (Ubuntu) BugBuddy Version: 2.23.91 System: Linux 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499906 Selinux: No Accessibility: Disabled GTK+ Theme: NewHuman 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 --------------------- x-session-manager[7334]: DEBUG(+): GsmManager: Client removed: /org/gnome/SessionManager/Client33 x-session-manager[7334]: DEBUG(+): GsmClient: disposing /org/gnome/SessionManager/Client33 x-session-manager[7334]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x84f1cb0 [nautilus 10f2f92167dbc328dd12203636939163700000073340066]) ERROR: Couldn't attach to DCOP server! ERROR: Couldn't attach to DCOP server! ERROR: Couldn't attach to DCOP server! ERROR: Couldn't attach to DCOP server! ERROR: Couldn't attach to DCOP server! Nautilus-Share-Message: Called "net usershare info" but it failed: "net usershare" ha restituito l'errore 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Nessun fi Please ask your system administrator to enable user sharing. ERROR: Couldn't attach to DCOP server! (gnome-panel:7410): Gtk-WARNING **: Attempting to add a widget with type GtkAccelLabel to a GtkImageMenuItem, but as a GtkBin subclass a GtkImageMenuItem can only contain one widget at a time; it alre ERROR: Couldn't attach to DCOP server! -------------------------------------------------- Traceback (most recent call last):
+ Trace 206158
gtk.gdk.threads_init()
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 544946 ***