Konqueror 4.2.2 crashes when accessing "https://www.fortisbanking.be"

[Massimiliano Lentini]

Binary package hint: konqueror

When I try to acces " https://www.fortisbanking.be " Konqueror hangs up, in Kubuntu 9.04 Jaunty.
With webkit in Konqueror can I acces the site With KHTML no.
In the earlier versions of Konqueror I didn't have problems

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Massimiliano Lentini (massimo21)]

The same happens with hotmail.
When I use webkit it works fine but it won't with KHTML.

[Jonathan Thomas (echidnaman)]

Is it enough to just visit this page or does one have to log in? Everything works fine for me with KDE 4.3 beta2.
Also, could you please install kdebase-dbg and get a crash log from the KDE crash handler? (Click the details checkbox in the crash handler in KDE 4.2)

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Massimiliano Lentini (massimo21)]

I tryed to launch konqueror with konsole and this is what i get when I log in www.fortisbanking.be

QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::pen: Painter not active
QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'

I want to ad that I work whit kubuntu 9.04 amd64.

and I tryed it also whit a fresh install of kubuntu 9.10 amd64 alpha5 and the problem is still there.

I get no crash report of the KDE crash handler because it only freesez (I think).

[Jonathan Thomas (echidnaman)]

Ok, we could try to get the report manually then. Could you install kdebase-dbg and try to obtain the backtrace following the instructions at https://wiki.kubuntu.org/Backtrace please? Thanks in advance.

[Massimiliano Lentini (massimo21)]

This is my result

massy@massy-desktop:~$ gdb konqueror 2>&1 | tee ~/gdb-konqueror.txt
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/konqueror
[Thread debugging using libthread_db enabled]
[New Thread 0x7fcfb6786750 (LWP 5167)]
konqueror(5167) KonqViewManager::setCurrentProfile: "webbrowsing" localPath= "/home/massy/.kde/share/apps/konqueror/profiles/webbrowsing"
[New Thread 0x7fcfa38d9950 (LWP 5171)]
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setClipRegion: Painter not active
QPainter::setClipRegion: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setClipRegion: Painter not active
QPainter::hasClipping: Painter not active ...

[Jonathan Thomas (echidnaman)]

No, not really. Could you run "bt all" from gdb when konqueror crashes? Thanks.

[Jonathan Thomas (echidnaman)]

Sorry, "bt full"

[Massimiliano Lentini (massimo21)]

This is it.

massy@massy-desktop:~$ gdb konqueror 2>&1 | tee ~/gdb-konqueror.txt
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/konqueror
[Thread debugging using libthread_db enabled]
[New Thread 0x7f4fcda43750 (LWP 5449)]
[New Thread 0x7f4fbab7f950 (LWP 5462)]
QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'
QColor::setNamedColor: Unknown color name 'transparant'
konqueror(5449) KHTMLRun::foundMimeType: finished
konqueror(5449) KHTMLRun::foundMimeType: finished
konqueror(5449) KHTMLRun::foundMimeType: finished
konqueror(5449) KHTMLRun::foundMimeType: finished
QColor::setNamedColor: Unknown color name 'transparant'
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::drawRects: Painter not active ...

[Jonathan Thomas (echidnaman)]

And kdelibs5-dbg is installed?

[Massimiliano Lentini (massimo21)]

I repeated it on another pc and i checked that kdelibs5-lib was installed,
I attached the txt file.
The actualy URL that makes Konqueror crash is "https://www.fortisbanking.be/private/start.asp"
Hope that this helps better.

[Jonathan Thomas (echidnaman)]

Oh, man. I'm really sorry I keep asking you to do things. The backtrace is really good now too.

..but... could you try with KDE 4.3.2 (http://www.kubuntu.org/new/kde-4.3.2) please? I wouldn't feel comfortable forwarding this report to KDE without knowing whether or not the crash is still an issue in the latest version of KDE. Thanks for hanging in there.

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!