Bug 103772

Summary: konqueror, svgdisplay crashes on particular svg
Product: ksvg Reporter: Balachandran Chandrasekharan <balachandran_c>
Component: generalAssignee: Nikolas Zimmermann <wildfox>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: cfeck, esigra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Backtrace from konqueror.
The image that causes the crash.
konqueror svg crash

Description Balachandran Chandrasekharan 2005-04-13 07:30:21 UTC
Version:           3.4.0-0pre1 (using KDE KDE 3.3.91)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The apps konqueror and svgdisplay crash upon loading the particular svg image. Both of them give the same backtrace. Backtrace and image are attached.
Comment 1 Balachandran Chandrasekharan 2005-04-13 07:31:44 UTC
Created attachment 10599 [details]
Backtrace from konqueror.
Comment 2 Balachandran Chandrasekharan 2005-04-13 07:33:08 UTC
Created attachment 10600 [details]
The image that causes the crash.
Comment 3 Tommi Tervo 2005-04-25 15:54:06 UTC
Program received signal SIGABRT, Aborted.
#5  0x2a311ef8 in KSVG::KSVGLoader::slotResult (this=0x82e6380, job=0x82bea00)
    at KSVGLoader.cpp:192
No locals.
#6  0x2a310559 in KSVG::KSVGLoader::qt_invoke (this=0x82e6380, _id=3,
    _o=0xbfbfeda4) at KSVGLoader.moc:133
        this = (KSVGLoader *) 0x82e6380
#7  0x28e6ef01 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3
No symbol table info available.
#8  0x2840c3c0 in KIO::Job::result (this=0x82bea00, t0=0x82bea00)
    at jobclasses.moc:156
        this = (Job *) 0x82bea00
        clist = (QConnectionList *) 0x82df3c0
        o = {{type = 0x29263fc8, payload = {b = false, c = 0 '\000', s = 5376,
#11 0x283fb5b1 in KIO::TransferJob::slotFinished (this=0x82bea00)
    at job.cpp:899
        this = (TransferJob *) 0x82bea00
#12 0x2840f23f in KIO::TransferJob::qt_invoke (this=0x82bea00, _id=17,
    _o=0xbfbff04c) at jobclasses.moc:1050
No locals.
#13 0x28e6ef01 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3
No symbol table info available.
#14 0x28e6edf5 in QObject::activate_signal () from /usr/X11R6/lib/libqt-mt.so.3
No symbol table info available.
#15 0x283efb51 in KIO::SlaveInterface::finished (this=0x8335f00)
    at slaveinterface.moc:226
        this = (SlaveInterface *) 0x8335f00
Comment 4 Stephan Hermann 2006-01-11 18:32:06 UTC
Created attachment 14216 [details]
konqueror svg crash

Same happens with this svg from
http://www.croczilla.com/svg/samples/svgtetris/svgtetris.svg.

The distro specific bug is filed in
http://bugzilla.ubuntu.com/show_bug.cgi?id=20361.

Regards,

\sh
Comment 5 Yuriy Kozlov 2006-12-20 22:04:27 UTC
I get this error in Opera on the attached image that makes Konqueror crash:

"XML parsing failed: syntax error (Line: 11, Character: 1)

Error:undeclared XML namespace prefix used in attribute name
Specification:http://www.w3.org/TR/REC-xml/#nsc-NSDeclared"

The tetris svg loads fine in Opera.

Both make Konqueror crash on KDE 3.5.5
Comment 6 Juan Carlos Torres 2007-03-14 15:37:32 UTC
This crash is still happening on KDE 3.5.6 on Kubuntu.
Comment 7 patch_linams 2007-07-26 10:41:49 UTC
Actually, there are two bugs in this bug report, take a look at two different backtraces:

1) http://bugs.kde.org/attachment.cgi?id=10599&action=view

2) http://bugs.kde.org/attachment.cgi?id=14216&action=view


The first one was attached by the reporter and is for the same bug as

http://bugs.kde.org/show_bug.cgi?id=126176

The second one is entirely different.
Comment 8 patch_linams 2007-07-26 11:53:41 UTC
The second one is this bug

http://bugs.kde.org/show_bug.cgi?id=116155.

It looks like the original bug and bug http://bugs.kde.org/show_bug.cgi?id=126176 can be closed (they are the same).
Comment 9 esigra 2009-01-18 10:44:18 UTC
This is a confirmation that the bug still exists in KDE 3.5.10.
Comment 10 Christoph Feck 2011-10-17 21:06:51 UTC
This component has been replaced with the QtSvg based "svgpart" in KDE 4. If
this issue still needs to be addressed, please add a comment.