After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574022 - crash in Epiphany Web Browser: using jijdo-lite and fil...
crash in Epiphany Web Browser: using jijdo-lite and fil...
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-04 03:23 UTC by henri.degraaf
Modified: 2009-03-04 07:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description henri.degraaf 2009-03-04 03:23:26 UTC 
Version: 2.22.3

What were you doing when the application crashed?
using jijdo-lite and filezilla in windows 2 and 3 respectivly


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The XFree86 Project, Inc
X Vendor Release: 40300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 105873408 vsize: 105873408 resident: 52269056 share: 21368832 rss: 52269056 rss_rlim: 4294967295
CPU usage: start_time: 1236136711 rtime: 685 utime: 575 stime: 110 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin//epiphany-browser'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6b40700 (LWP 3088)]
0xb7fca424 in __kernel_vsyscall ()

+ Trace 213137

Thread 1 (Thread 0xb6b40700 (LWP 3088))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #7 <signal handler called>
  • #8 ??
  • #9 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 194
  • #10 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #11 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #12 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #13 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #14 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #15 g_io_unix_dispatch
  • #16 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #17 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #18 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #19 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #20 main
    at /build/buildd-epiphany-browser_2.22.3-9-i386-MLTyHU/epiphany-browser-2.22.3/src/ephy-main.c line 753
  • #0 __kernel_vsyscall 


----------- .xsession-errors (22 sec old) ---------------------
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
** (gnome-settings-daemon:3247): WARNING **: numlock: XkbQueryExtension returned an error
** (gnome-settings-daemon:3247): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available,
no way to support keyboard autorepeat rate settings
** (gnome-settings-daemon:3247): WARNING **: Unable to start a11y_keyboard manager: XKB functionality is disabled.
Shutdown failed or nothing to shut down.
<stdin>:130:14: warning: missing terminating ' character
** (gnome-screensaver:3271): WARNING **: screensaver already running in this session
--------------------------------------------------
Comment 1 Xan Lopez 2009-03-04 07:28:17 UTC 

*** This bug has been marked as a duplicate of 509083 ***