Your message dated Wed, 24 Mar 2010 17:40:35 +0100
with message-id <201003241740.35597.ewoer...@kde.org>
and subject line Re: koqnueror crashes reproducibly on loading excite mail
has caused the Debian Bug report #517547,
regarding koqnueror crashes reproducibly on loading excite mail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
517547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: konqueror
Version: 4:3.5.9.dfsg.1-6
Severity: ciritical
How to reproduce:
1. Assume you have an email account at excite (if none, try to create a free
one without crashing, if you crash - you've triggered the bug).
2. Go to http://www.excite.com/
3. Click on "My Email"
4. Login into your account using secure option (if no automatic login has been
arranged), confirming changing from a https to a http page
5. During the load of the web interface (the load bar showing the precentage of
the load) a crash happens
The unexpected termination was noticed by KDE, and a stack trace was produced:
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb68226c0 (LWP 4367)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x006c0065 in ?? ()
#7 0xb6057f5a in ?? () from /usr/lib/libkhtml.so.4
#8 0x09d29888 in ?? ()
#9 0x090c02d8 in ?? ()
#10 0xbfe367b8 in ?? ()
#11 0xb6080f5f in QPtrList<khtml::CSSOrderedRule>::deleteItem ()
from /usr/lib/libkhtml.so.4
Backtrace stopped: frame did not save the PC
The computer has a fresh installed lenny.
$ aptitude show libc6 | grep Version
Version: 2.7-18
$ uname -s -r -v -m -p -i -o
Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 unknown unknown
GNU/Linux
Since excite mail is a widely used resource on the internet, I've decided to
raise the security to critical. I'm able to reproduce the crash.
Regards
Sasha.
------------------------------------------------------------
Foreclosure Help
Stop foreclosure. Click here to stay in your home and rebuild credit.
http://tagline.excite.com/fc/FgElN1gw8RkifExZljJquP0qebyQZCOgDL62AcZyoEDM2j5F8Y0lhyYPf1m/
--- End Message ---
--- Begin Message ---
Version: 4:4.2.0-1
The bug you reported has been fixed in KDE SC 4.2
--- End Message ---
