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 456852 - Epiphany crashes when pressing ESC in address entry
Epiphany crashes when pressing ESC in address entry
Status: RESOLVED DUPLICATE of bug 457384
Product: epiphany
Classification: Core
Component: General
2.19.x
Other All
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-07-14 13:08 UTC by Frédéric Bellaiche
Modified: 2007-07-19 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Frédéric Bellaiche 2007-07-14 13:08:46 UTC 
Steps to reproduce:
1. Start typing a new URL (at least 1 char)
2. Press ESC
3. Boom ...

Stack trace:
From bug-buddy:

Distribution: LFS
Gnome Release: 2.19.5 2007-07-09 
BugBuddy Version: 2.18.1

System: Linux 2.6.21.1 #1 SMP PREEMPT Sat May 12 19:51:18 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: OrangoTango

Memory status: size: 161492992 vsize: 161492992 resident: 38645760 share: 28622848 rss: 38645760 rss_rlim: 4294967295
CPU usage: start_time: 1184418089 rtime: 159 utime: 143 stime: 16 cutime:0 cstime: 0 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 -1211455824 (LWP 7191)]
[New Thread -1332298848 (LWP 7203)]
[New Thread -1296835680 (LWP 7199)]
[New Thread -1288442976 (LWP 7198)]
[New Thread -1280050272 (LWP 7197)]
[New Thread -1271657568 (LWP 7196)]
[New Thread -1250911328 (LWP 7193)]
[New Thread -1232725088 (LWP 7192)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 147981

Thread 1 (Thread -1211455824 (LWP 7191))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 865
  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 493
  • #5 IA__g_log
    at gmessages.c line 517
  • #6 IA__g_return_if_fail_warning
    at gmessages.c line 532
  • #7 IA__gtk_entry_set_text
    at gtkentry.c line 4378
  • #8 gtk_entry_completion_key_press
    at gtkentry.c line 5909
  • #9 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 gtk_widget_event_internal
    at gtkwidget.c line 4268
  • #15 gtk_entry_completion_popup_key_event
    at gtkentrycompletion.c line 840
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #20 IA__g_signal_emit
    at gsignal.c line 2243
  • #21 gtk_widget_event_internal
    at gtkwidget.c line 4268
  • #22 IA__gtk_propagate_event
    at gtkmain.c line 2291
  • #23 IA__gtk_main_do_event
    at gtkmain.c line 1537
  • #24 gdk_event_dispatch
    at gdkevents-x11.c line 2349
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #26 g_main_context_iterate
    at gmain.c line 2694
  • #27 IA__g_main_loop_run
    at gmain.c line 2898
  • #28 IA__gtk_main
    at gtkmain.c line 1144
  • #29 main
    at ephy-main.c line 723
  • #0 __kernel_vsyscall 




Other information:
Comment 1 Reinout van Schouwen 2007-07-16 13:19:37 UTC 
It works for me. What page were you on when the crash occured? Could you try with a more recent Mozilla back-end?
Comment 2 Reinout van Schouwen 2007-07-19 14:51:51 UTC 
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 457384 ***