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 567674 - crash in Epiphany Web Browser: subiendo fotos y poniend...
crash in Epiphany Web Browser: subiendo fotos y poniend...
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-01-13 22:38 UTC by 2005.alegre
Modified: 2009-01-13 23:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description 2005.alegre 2009-01-13 22:38:16 UTC 
Version: 2.22.3

What were you doing when the application crashed?
subiendo fotos y poniendo titulo


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

System: Linux 2.6.26-1-486 #1 Mon Dec 15 17:32:01 UTC 2008 i586
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 137076736 vsize: 137076736 resident: 45240320 share: 24682496 rss: 45240320 rss_rlim: 4294967295
CPU usage: start_time: 1231885283 rtime: 15790 utime: 14393 stime: 1397 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 0xb6b78700 (LWP 4118)]
0xb71fe3d1 in waitpid () from /lib/libpthread.so.0

+ Trace 211535

Thread 1 (Thread 0xb6b78700 (LWP 4118))

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


----------- .xsession-errors (123 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** (epiphany-browser:4306): WARNING **: An error occured while calling remote method: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus sec
--------------------------------------------------
Comment 1 Reinout van Schouwen 2009-01-13 23:04:57 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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