GNOME Bugzilla – Bug 543137
crash in Deskbar: After enter phrase 'test...
Last modified: 2008-07-16 20:01:06 UTC
What were you doing when the application crashed? After enter phrase 'test' to deskbar deskabr hangs. Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25.9-76.fc9.x86_64 #1 SMP Fri Jun 27 15:58:30 EDT 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10499905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora 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 (11 sec old) --------------------- compiz (mag) - Warn: Could not load magnifier overlay image "Gnome/overlay.png"! compiz (trailfocus) - Warn: Attempting to define start higher than max windows. compiz (trailfocus) - Warn: Attempting to define start higher than max windows. compiz (trailfocus) - Warn: Attempting to define start higher than max windows. compiz (trailfocus) - Warn: Attempting to define start higher than max windows. compiz (core) - Error: no 'text' plugin with ABI version '20080421' loaded compiz (scalefilter) - Warn: No compatible text plugin found. (liferea:3078): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed Liferea did receive signal 11 (Naruszenie ochrony pamięci). ** (gnome-panel:3018): WARNING **: Failed to establish a connection with GDM: Nie ma takiego pliku ani katalogu Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3933--545433896-1216142978 --active --geometry 80x24+255+185 --title pholuj@khazad:~ --wor -------------------------------------------------- Traceback (most recent call last):
+ Trace 202910
self.beagle.send_request_async(snippet_request)
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 530057 ***