Red Hat Bugzilla – Bug 234323
konqueror crashes when zooming in "too much"
Last modified: 2008-05-06 15:26:11 EDT
Description of problem:
konqueror crashes when zooming in "too much" when
view mode is set to "icon view" or "tree view"
(maybe others are affected as well).
subsequent launch attempts fail until manual cleanup
of konqiconviewrc and friends. IconSize=64 is lethal -
setting it back to 32 cures the problem.
Version-Release number of selected component (if applicable):
always (on my system :-)
Backtrace is telling something about SVGxxxxx but I dont
want to kill konqueror while I am just typing in this text..
i have tried with different size and it works for me. I cannot reproduce this
problem on my machine with FC6-update.
Could you please make sure that you have installed KDE packages from
could you please attach the output of "rpm -qa | grep kde"? Thanks
Here you are. I will try the same on my home machine this evening.
Created attachment 151217 [details]
konqueror crash backtrace - no debug symbols
On my home system it does indeed not crash.
(office and home system are uptodate)
Today I crated a new user on my office system, switch-desked to KDE.
same crash. see the attached file backtrace.
It depends on the directory contents. In the home directory (a
few files only) it does not crash, in /tmp (lots of garbage) it crashes.
This bug report should become a bad example of
how to not report a problem.
What a poor description of a problem!!!
Not a single time anyone mentions that you have
to use MOUSE and CLICK on the ENLARGE FONTS icon
on the Main Tool bar.
No wonder Than cannot reproduce it.
You don't need to click enlarge fonts. You just need to enable larger icons at
some point, maybe even before you actually upgraded to FC6. Also, just enabling
larger icons does not trigger this; the problem went away for me when I switched
to keramik style.
Which means that all icons (even when big) crash konqueror in FC6; However one
which definetely does is /usr/share/icons/gnome/scalable/mimetypes/tgz.svg
So, enable large icons, switch to bluecurve style and use konqueror to navigate
to a directory which has a .tgz file and then it crashes. Probably other icons
too, but tgz.svg is the one which triggered this thing for me.
Bug #236864 seems to be a duplicate of this bug.
argh, I tried to write that _not_ all icons crash konqueror. Sorry about the noise.
I don't think this is the same as Bug 236864.
My example is that konqueror crashes when it looks at a directory containing a
.zip file. It is also .bz2 and .rpm files according to some-one else:
The crash error message is:
konqueror: art_render_gradient.c:338: art_render_gradient_linear_render_8:
Assertion `offset_fraction <= stops[ix].offset' failed.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = konqueror path = <unknown> pid = 3347
This happens to me when trying to display directories which contain *.rpm or
*.tar.bz2 files at a icon size setting of "very large". Probably this is
connected to the icon.
Bluecurve icon theme from redhat-artwork-5.0.8-1.fc6
The problem disappears when switching to the "Crystal SVG" icon theme. It comes
again when using the "Bluecurve" icon theme.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.