GNOME Bugzilla – Bug 478281
crash in Epiphany Web Bookmarks: I've pressed the 'refres...
Last modified: 2007-09-19 07:59:28 UTC
Version: 2.18.3 What were you doing when the application crashed? I've pressed the 'refresh' button on the 'Adblock' plugin preferences page, which should refresh the rule set from the net Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-09-10 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r5 #1 SMP Tue Sep 11 02:25:44 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Xfce Icon Theme: gnome Memory status: size: 454336512 vsize: 454336512 resident: 81219584 share: 41545728 rss: 81219584 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190187454 rtime: 593 utime: 545 stime: 48 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47158622004016 (LWP 4047)] [New Thread 1132497216 (LWP 4173)] [New Thread 1140889920 (LWP 4172)] [New Thread 1124104512 (LWP 4081)] [New Thread 1115711808 (LWP 4080)] [New Thread 1090533696 (LWP 4054)] [New Thread 1082140992 (LWP 4053)] 0x00002ae3f70dbb0f in __libc_waitpid (pid=4198, stat_loc=0x7fffb912200c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 163933
Thread 1 (Thread 47158622004016 (LWP 4047))
----------- .xsession-errors (339506 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 [plug] [atelnetui] Unable to launch server. Stack trace is : A cím már használatban van ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
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 452119 ***