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 417731 - crash in Epiphany Web Browser:
crash in Epiphany Web Browser:
Status: RESOLVED DUPLICATE of bug 413550
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-03-13 02:36 UTC by kh
Modified: 2007-03-13 08:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description kh 2007-03-13 02:36:13 UTC
Version: 2.16.3

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:05:34 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 866701312 vsize: 866701312 resident: 54345728 share: 29208576 rss: 54345728 rss_rlim: -1
CPU usage: start_time: 1173753337 rtime: 168 utime: 155 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496511456 (LWP 11066)]
(no debugging symbols found)
0x00000037d960d96f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496511456 (LWP 11066))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 nsSupportsWeakReference::~nsSupportsWeakReference\$base
    from /usr/lib64/firefox-1.5.0.10/libgtkembedmoz.so
  • #3 <signal handler called>
  • #4 ??
  • #5 PR_NewRWLock
    from /usr/lib64/libnspr4.so
  • #6 PR_ProcessExit
    from /usr/lib64/libnspr4.so
  • #7 PR_ProcessExit
    from /usr/lib64/libnspr4.so
  • #8 __cxa_pure_virtual
    from /usr/lib64/libnspr4.so
  • #9 ??
  • #10 _fini
    from /usr/lib64/libnspr4.so
  • #11 ??
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (48 sec old) ---------------------
LibClamAV Warning: ********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.  ***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/faq.html ***
LibClamAV Warning: ********************************************************
LoadPlugin: failed to initialize shared library /home/hikami/.mozilla/plugins/npwrapper.libflashplayer.so [/home/hikami/.mozilla/plugins/npwrapper.libflashplayer.so: wrong ELF class: ELFCLASS64]
LoadPlugin: failed to initialize shared library /home/hikami/.mozilla/plugins/npwrapper.nppdf.so [/home/hikami/.mozilla/plugins/npwrapper.nppdf.so: wrong ELF class: ELFCLASS64]
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
core: bindWindow(): XGetWindowAttributes() returned non-success.Window: 0x5401A04
core: bindWindow(): XGetWindowAttributes() returned non-success.Window: 0x5401A04
Error: Duplicate name found: replacing MatchId 99544 with 99676
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-03-13 08:13:26 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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