GNOME Bugzilla – Bug 454419
crash in XChat-GNOME IRC Chat: doing nothing related to...
Last modified: 2007-07-07 20:42:03 UTC
What were you doing when the application crashed? doing nothing related to it -- browsing internet, etc. seemed to have crashed based on something from the network Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7.genneth #1 SMP Fri Jun 29 12:16:24 BST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 188194816 vsize: 188194816 resident: 52379648 share: 42663936 rss: 52379648 rss_rlim: 4294967295 CPU usage: start_time: 1183490243 rtime: 73054 utime: 65101 stime: 7953 cutime:4919 cstime: 14369 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/xchat-gnome' (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 -1209030944 (LWP 15462)] (no debugging symbols found) 0x007a9402 in __kernel_vsyscall ()
+ Trace 146224
Thread 1 (Thread -1209030944 (LWP 15462))
----------- .xsession-errors (115192 sec old) --------------------- File /home/genneth/Progs/XB/generate has finished changing flushing all words Finished indexing. Waiting for new events... File /home/genneth/Progs/XB/generate has finished changing flushing all words Finished indexing. Waiting for new events... no matching pair found for inotify move event for /home/genneth/Progs/XB/Main.hs File /home/genneth/Progs/XB/Main.hs has finished changing flushing all words Finished indexing. Waiting for new events... no matching pair found for inotify move event for /home/genneth/Progs/XB/FSTree.hs File /home/genneth/Progs/XB/FSTree.hs has finished changing flushing all words ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 431990 ***