GNOME Bugzilla – Bug 474887
crash in Help: パネルのシステムから、fedoraについてを見よ...
Last modified: 2008-01-13 16:47:24 UTC
Version: 2.18.1 What were you doing when the application crashed? パネルのシステムから、fedoraについてを見ようとクリックした。 Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 65937408 vsize: 65937408 resident: 17170432 share: 11177984 rss: 17170432 rss_rlim: 4294967295 CPU usage: start_time: 1189268357 rtime: 198 utime: 164 stime: 34 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/yelp' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208817952 (LWP 2932)] [New Thread -1212167280 (LWP 2933)] (no debugging symbols found) 0x00e23402 in __kernel_vsyscall ()
+ Trace 161359
Thread 1 (Thread -1208817952 (LWP 2932))
----------- .xsession-errors (16 sec old) --------------------- SCIM has been successfully launched. Smart Common Input Method 1.4.5 could not attach to desktop process /usr/sbin/pup:60: GtkWarning: Failed to set text from markup due to error parsing markup: 行 1 の 20 文字目でエラー: おかしな文字 '\' です。属性 'size' (エレメント 'span') の self.pupxml = gtk.glade.XML(fn, domain="pirut") Loading "installonlyn" plugin ** (nautilus:2468): WARNING **: ファイル 'computer:///Filesystem.desktop' の保存中にエラー: 許可されていない操作です ** (nautilus:2468): WARNING **: ファイル 'computer:///Filesystem.desktop' の保存中にエラー: 許可されていない操作です Yelp-ERROR **: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the netwo aborting... --------------------------------------------------
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report. *** This bug has been marked as a duplicate of 364790 ***