GNOME Bugzilla – Bug 620090
SIGSEGV: No such file or directory in JSCell.cpp when I try to log in to linkedin.com
Last modified: 2010-06-25 10:50:41 UTC
My epiphany browser crashes whenever I try to enter my password in to linkedin.com. I am using epiphany 2.30.2 on Debian Sid. == Steps to reproduce == 1) start epiphany 2) Open the url www.linkedin.com 3) Press the link "sign in" 4) Try to log in == Backtrace == niels@langager:~ $ gdb epiphany-browser warning: Not importing directory 'os': missing __init__.py GNU gdb (GDB) 7.1-debian Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/epiphany-browser...Reading symbols from /usr/lib/debug/usr/bin/epiphany-browser...done. done. (gdb) r [Thread debugging using libthread_db enabled] [New Thread 0xb0e1bb70 (LWP 4080)] [New Thread 0xb04f2b70 (LWP 4081)] [New Thread 0xafaffb70 (LWP 4082)] [Thread 0xafaffb70 (LWP 4082) exited] [New Thread 0xafaffb70 (LWP 4083)] [New Thread 0xae6f3b70 (LWP 4084)] [Thread 0xae6f3b70 (LWP 4084) exited] [Thread 0xafaffb70 (LWP 4083) exited] [New Thread 0xafaffb70 (LWP 4085)] [New Thread 0xae6f3b70 (LWP 4086)] [New Thread 0xad0bfb70 (LWP 4087)] [Thread 0xafaffb70 (LWP 4085) exited] [Thread 0xae6f3b70 (LWP 4086) exited] [Thread 0xad0bfb70 (LWP 4087) exited] ** (epiphany:4077): DEBUG: NP_Initialize ** (epiphany:4077): DEBUG: NP_Initialize succeeded ** (epiphany:4077): DEBUG: NP_Initialize ** (epiphany:4077): DEBUG: NP_Initialize succeeded ** (epiphany:4077): DEBUG: NP_Initialize ** (epiphany:4077): DEBUG: NP_Initialize succeeded ** (epiphany:4077): DEBUG: NP_Initialize ** (epiphany:4077): DEBUG: NP_Initialize succeeded ^[[6~[New Thread 0xad0bfb70 (LWP 4088)] [New Thread 0xae6f3b70 (LWP 4089)] [New Thread 0xafaffb70 (LWP 4090)] [Thread 0xae6f3b70 (LWP 4089) exited] [Thread 0xafaffb70 (LWP 4090) exited] [Thread 0xad0bfb70 (LWP 4088) exited] Program received signal SIGSEGV, Segmentation fault. 0xb7733694 in JSC::JSCell::put (this=0xad792800, exec=0xad9385e4, identifier=..., value=..., slot=...) at ../JavaScriptCore/runtime/JSCell.cpp:143 143 ../JavaScriptCore/runtime/JSCell.cpp: No such file or directory. in ../JavaScriptCore/runtime/JSCell.cpp (gdb) ~ Undefined command: "". Try "help". (gdb) bt
+ Trace 222160
== Version == langager:/home/niels# dpkg -l | grep epiphany | grep ii ii epiphany 0.7.0-4 clone of Boulder Dash game ii epiphany-browser 2.30.2-2 Intuitive GNOME web browser ii epiphany-browser-data 2.30.2-2 Data files for the GNOME web browser ii epiphany-browser-dbg 2.30.2-2 Debugging symbols for the GNOME web browser ii epiphany-data 0.7.0-4 required data files for epiphany game ii epiphany-extensions 2.30.1-1 Extensions for Epiphany web browser langager:/home/niels# dpkg -l | grep libdbus | grep ii ii libdbus-1-3 1.2.24-1 simple interprocess messaging system ii libdbus-1-dev 1.2.24-1 simple interprocess messaging system (development headers) ii libdbus-c++-1-0 0~20090907-1 C++ API for D-BUS (runtime package) ii libdbus-glib-1-2 0.86-1 simple interprocess messaging system (GLib-based shared library) ii libdbus-glib-1-2-dbg 0.86-1 simple interprocess messaging system (GLib library debug symbols ii libdbus-glib-1-dev 0.86-1 simple interprocess messaging system (GLib interface) langager:/home/niels# dpkg -l | grep keyring | grep ii ii debian-archive-keyring 2009.01.31 GnuPG archive keys of the Debian archive ii gnome-keyring 2.30.1-2 GNOME keyring services (daemon and tools) ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libpam-gnome-keyring 2.30.1-2 PAM module to unlock the GNOME keyring upon login ii python-gnomekeyring 2.30.0-1+b1 Python bindings for the GNOME keyring library langager:/home/niels# == A few warnings from .xsession-errors == ** (epiphany:2420): DEBUG: NP_Initialize ** (epiphany:2420): DEBUG: NP_Initialize succeeded ** (epiphany:2420): DEBUG: NP_Initialize ** (epiphany:2420): DEBUG: NP_Initialize succeeded ** (epiphany:2420): DEBUG: NP_Initialize ** (epiphany:2420): DEBUG: NP_Initialize succeeded ** (epiphany:2420): DEBUG: NP_Initialize ** (epiphany:2420): DEBUG: NP_Initialize succeeded (epiphany:2420): Gtk-CRITICAL **: gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed (epiphany:2420): Gtk-CRITICAL **: gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed (epiphany:2420): Gtk-CRITICAL **: gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed (epiphany:2420): Gtk-CRITICAL **: gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed (xchat-gnome:2457): Gdk-CRITICAL **: _gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat-gnome:2457): Gdk-CRITICAL **: _gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat-gnome:2457): Gdk-CRITICAL **: _gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed (xchat-gnome:2457): Gdk-CRITICAL **: _gdk_pixmap_new: assertion `(width != 0) && (height != 0)' faile:
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
sometimes when loading a page w/ saved username/password, that also happens to use JS to focus() the username field on page load, i get the following segfault, with ubuntu package version 2.30.2-1ubuntu1.1 : Program received signal SIGSEGV, Segmentation fault. 0x00007ffff5317877 in JSC::JSCell::put (this=<value optimized out>, exec=0x7fffe376abc8, identifier=..., value=..., slot=<value optimized out>) at ../JavaScriptCore/runtime/JSCell.cpp:143 143 ../JavaScriptCore/runtime/JSCell.cpp: No such file or directory. in ../JavaScriptCore/runtime/JSCell.cpp (gdb) t a a bt
+ Trace 222562
Thread 1 (Thread 0x7ffff7fb4800 (LWP 4374))
does the stacktrace i attached have enough info, or do i need to install the gnome-keyring dbg package?
For the record, there is no gnome-keyring-dbg in debian, but the following bug report contains a patch to control.in that alledgedly makes gnome-keyring-dbg appear. I haven't tried it out yet. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576231
*** This bug has been marked as a duplicate of bug 618355 ***