GNOME Bugzilla – Bug 543589
crash in Epiphany Web Bookmarks: Just browsing, I'm not a...
Last modified: 2009-04-25 08:26:40 UTC
Version: 2.22.3 What were you doing when the application crashed? Just browsing, I'm not aware of anything special... Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 361742336 vsize: 361742336 resident: 215932928 share: 36093952 rss: 215932928 rss_rlim: 4294967295 CPU usage: start_time: 1216329104 rtime: 166390 utime: 157363 stime: 9027 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' [Thread debugging using libthread_db enabled] [New Thread 0xb6b6e700 (LWP 19347)] [New Thread 0xb2c7ab90 (LWP 2310)] [New Thread 0xadba3b90 (LWP 2285)] [New Thread 0xb5ae6b90 (LWP 26736)] [New Thread 0xb1fceb90 (LWP 19362)] [New Thread 0xb39acb90 (LWP 19356)] [New Thread 0xb49aeb90 (LWP 19355)] [New Thread 0xb41adb90 (LWP 19354)] 0xb7f50424 in __kernel_vsyscall ()
+ Trace 203177
Thread 1 (Thread 0xb6b6e700 (LWP 19347))
----------- .xsession-errors (85107 sec old) --------------------- ![1216301241,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301241,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301241,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301241,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301241,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1216301250,000,xklav ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This trace indicates that Mozilla (which was being used by the program) was responsible for the crash, or alternatively that the program was compiled against a different version of Mozilla. Make sure the program was built against the most recent mozilla, and if you can duplicate the crash in mozilla itself, report the bug to https://bugzilla.mozilla.org/
*** Bug 544332 has been marked as a duplicate of this bug. ***
Reporters, please check if a bug is already filed in bugzilla.mozilla.org for this crash. If not, could you file one?
*** Bug 544361 has been marked as a duplicate of this bug. ***
I was not able to reproduce this with plain Mozilla...
I reported 544361 which has been marked as a duplicate of this one. I cannot reproduce it in Firefox nor Mozilla either.
It can still be a bug in the Gecko (Firefox or XULRunner) back-end, even though the crash isn't reproducable in Firefox itself. Hence, it should be reported to Mozilla bugzilla.
I have reported it as #447719, https://bugzilla.mozilla.org/show_bug.cgi?id=447719
*** Bug 551979 has been marked as a duplicate of this bug. ***
*** Bug 556349 has been marked as a duplicate of this bug. ***
*** Bug 573331 has been marked as a duplicate of this bug. ***
*** Bug 574932 has been marked as a duplicate of this bug. ***
*** Bug 580199 has been marked as a duplicate of this bug. ***