Konqueror KDE4 - Web browser crashes on close

Bug #186132 reported by LionRock
10
Affects Status Importance Assigned to Milestone
kdebase-kde4 (Ubuntu)
Invalid
Low
Rich Johnson

Bug Description

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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 0xb649e6c0 (LWP 6239)]
(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)
(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)
0xb7fd2410 in __kernel_vsyscall ()
[Current thread is 0 (process 6239)]

Thread 1 (Thread 0xb649e6c0 (LWP 6239)):
#0 0xb7fd2410 in __kernel_vsyscall ()
#1 0xb7e3fba6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7e3f9b7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3 0xb79376b0 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4 0x00000001 in ?? ()
#5 0x00000000 in ?? ()
#0 0xb7fd2410 in __kernel_vsyscall ()

Im using latest Hary version and running KDE 3.5.8. This is happening from the last update.

Regards

Tags: kde4
Revision history for this message
Rich Johnson (nixternal) wrote :

Is this still occurring for you? I cannot reproduce this issue. Thank you!

Changed in kdebase:
assignee: nobody → nixternal
status: New → Incomplete
Revision history for this message
Lomig (dunwael) wrote :

That occurs everytime I close konqueror.

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found) x 23
[Thread debugging using libthread_db enabled]
[New Thread 0x7fede690f7a0 (LWP 8530)]
(no debugging symbols found) x 69
[KCrash handler]
#5 0x00007fede61070e5 in raise () from /lib/libc.so.6
#6 0x00007fede6108b40 in abort () from /lib/libc.so.6
#7 0x00007fede610042f in __assert_fail () from /lib/libc.so.6
#8 0x00007fedd83e68e9 in KHTMLGlobal::finalCheck ()
   from /usr/lib/kde4/lib/libkhtml.so.5
#9 0x00007fedd895d4aa in ?? () from /usr/lib/kde4/lib/kde4/libkhtmlpart.so
#10 0x00007fede59ec31a in QObjectCleanupHandler::clear ()
   from /usr/lib/libQtCore.so.4
#11 0x00007fede59ec397 in QObjectCleanupHandler::~QObjectCleanupHandler ()
   from /usr/lib/libQtCore.so.4
#12 0x00007fede610a160 in exit () from /lib/libc.so.6
#13 0x00007fede60f31cb in __libc_start_main () from /lib/libc.so.6
#14 0x0000000000400649 in _start ()
#0 0x00007fede6172ba0 in nanosleep () from /lib/libc.so.6

Using Hardy Kubuntu-KDE4 Beta 1 fresh install on amd64

Changed in kdebase-kde4:
status: Incomplete → New
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Can you see if this still happens on your machine/configuration:
a. on Hardy final + backports (KDE 4.0.5)
b. on Hardy + KDE4.1 beta or daily from PPA

Changed in kdebase-kde4:
status: New → Incomplete
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Last comment was at Lomig. That should probably have been a separate report.

@LionRock: Does this still happen with Hardy final and KDE 3.5.9? If so, please install kdebase-dbg and post a new backtrace.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Sorry, now that I look at your backtrace more carefully, it looks like this is Konqueror/KDE4 you are running? But on KDE3?

In that case, make that kdebase-dbg-kde4 instead of kdebase-dbg, and Lomig's likely is indeed the same crash.

Changed in kdebase-kde4:
importance: Undecided → Low
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

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!

Changed in kdebase-kde4:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.