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 561693 - crash in Epiphany Web Browser (Webkit): try to open svg file
crash in Epiphany Web Browser (Webkit): try to open svg file
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: Backend
2.22.x
Other All
: High critical
: ---
Assigned To: Xan Lopez
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-20 15:48 UTC by jsivek
Modified: 2008-11-25 13:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
bug buddy created after instaling webkit-dbg package (31.84 KB, text/plain)
2008-11-23 19:05 UTC, jsivek
Details

Description jsivek 2008-11-20 15:48:18 UTC
Version: 2.22.3

What were you doing when the application crashed?
try to open svg file


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: tish
Icon Theme: Gorilla

Memory status: size: 112623616 vsize: 112623616 resident: 34643968 share: 21540864 rss: 34643968 rss_rlim: 4294967295
CPU usage: start_time: 1227195892 rtime: 470 utime: 440 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb5264ae0 (LWP 2536)]
0xb7efa424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb5264ae0 (LWP 2536))

  • #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 <signal handler called>
  • #7 ??
    from /usr/lib/libwebkit-1.0.so.1
  • #8 ??
    from /usr/lib/libwebkit-1.0.so.1
  • #9 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (24671 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)
LoadPlugin: failed to initialize shared library /home/sivek/.mozilla/plugins/npatgpc.so [libstdc++.so.5: cannot open shared object file: No such file or directory]
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-11-21 09:13:21 UTC
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!
Comment 2 jsivek 2008-11-23 19:05:54 UTC
Created attachment 123278 [details]
bug buddy created after instaling webkit-dbg package
Comment 3 jsivek 2008-11-23 19:07:25 UTC
I have added new stack trace - bigger one:
Attachment #123278 [details]
Comment 4 Reinout van Schouwen 2008-11-25 13:20:39 UTC
Thanks for taking the time to report this bug. This trace indicates that WebKit (which was being used by the program) might be responsible for the crash. Make sure the program was built against a recent version of WebKit, and if you can still duplicate the crash, report the bug to http://bugs.webkit.org/ including a link to this bug report and noting the WebKit version/revision number. When reporting the WebKit bug, be sure to include '[GTK]' in the summary and use the 'gtk' keyword.