Bug 164766

Summary:	SIGSEGV Konqueror after booting openSUSE 11.0
Product:	[Applications] konqueror	Reporter:	Heinz Altschul <heinz.altschul>
Component:	general	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	finex, frank78ac
Priority:	NOR
Version:	4.0.4
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Heinz Altschul 2008-06-23 17:17:09 UTC

Version:           15.1 (using KDE 4.0.4)
Installed from:    SuSE RPMs
OS:                Linux

At the end of the boot procedere it opens a window Signal 11  SIGSEGV
When j open konqueror by clicking on the ikon, the programm starts and works correctly to my opinion.
The report "konqueror kcrash"

[?1034h(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 0xb64f38e0 (LWP 3118)]
(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)
(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  0xb7febced in ?? () from /usr/lib/libkdeinit4_konqueror.so
#7  0xb800ce98 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#8  0xb761d3fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0xb761d972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb3fdd527 in ?? () from /usr/lib/kde4/dolphinpart.so
#11 0xb3fdf493 in ?? () from /usr/lib/kde4/dolphinpart.so
#12 0xb761d3fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb761d972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb3fad5e7 in DolphinView::modeChanged ()
   from /usr/lib/libdolphinprivate.so.4
#15 0xb3fae9e6 in DolphinView::applyViewProperties ()
   from /usr/lib/libdolphinprivate.so.4
#16 0xb3fb0492 in DolphinView::updateView ()
   from /usr/lib/libdolphinprivate.so.4
#17 0xb3fb0558 in DolphinView::setUrl () from /usr/lib/libdolphinprivate.so.4
#18 0xb3fde351 in ?? () from /usr/lib/kde4/dolphinpart.so
#19 0xb7f29d5f in KParts::BrowserExtension::restoreState ()
   from /usr/lib/libkparts.so.4
#20 0xb7fba090 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#21 0xb7fba9a7 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#22 0xb7fc1c9a in ?? () from /usr/lib/libkdeinit4_konqueror.so
#23 0xb7fc11f7 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#24 0xb7fc262c in ?? () from /usr/lib/libkdeinit4_konqueror.so
#25 0xb7fc3651 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#26 0xb7ff60b7 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#27 0xb7c3ff4d in KMainWindow::readPropertiesInternal ()
   from /usr/lib/libkdeui.so.5
#28 0xb7c400f0 in KMainWindow::restore () from /usr/lib/libkdeui.so.5
#29 0xb802c378 in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#30 0x080487c2 in _start ()
#0  0xffffe430 in __kernel_vsyscall ()

Best regards  Heinz

Comment 1 FiNeX 2008-06-23 17:38:39 UTC

Please, use the packages with debug symbols, this is not useful. You'll find the instruction on this page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Anyway, are you able to reproduce the crash? If yes, could you exactly explain how to reproduce it?

Thanks a lot Heinz!

Comment 2 Heinz Altschul 2008-06-24 11:42:20 UTC

On window nr.one J have Konqueror open (active). J leve it aktiv when j switch off the system. When j restart (boot) the system, Konqueror does not start again, but there come the KDE-Crashmanager. Other programms like Terminal Konsole are starting again. If J start now Konqueror manualy by the ikon, it starts absolutly normal without any error. 
If J switch off the computer with emty windows, restart is correct with emty windows again.

Comment 3 FiNeX 2008-06-24 12:04:19 UTC

I cannot reproduce it using current trunk. It could have been fixed between the version packaged by openSUSE and current trunk. I'll leave this open for further confirmations.

Comment 4 A. Spehr 2008-06-24 12:21:31 UTC

http://bugs.kde.org/show_bug.cgi?id=156172 ? 
For 4.00.80, gone by now. Is this the same?

Comment 5 Heinz Altschul 2008-06-24 18:52:17 UTC

id-156172: J could not find any symilar problems as mentioned there.
My system has KDE Version 4.0.4 (KDE 4.0.4 >= 20080505) "release 15.1"

Comment 6 A. Spehr 2008-06-28 10:20:00 UTC

Can you get a backtrace? I suspect this is the same bug.

Comment 7 Heinz Altschul 2008-06-30 17:34:00 UTC

Unfortunately I am not programmer, so I got a nice task to learn about. I am just on the way to study papers about Debugging and "An application crashed". There is only one problem, because the error occurs only in the combination with the booting sequence. Is there eventually a problem with hardwareseed (2.4 GHz Procssor or the board (ASUS P5B)? 
Sorry for delayed answer.

Comment 8 Frank Reininghaus 2008-07-10 18:22:46 UTC

@comment #4, comment#6: I disagree. Neither the backtraces nor the descriptions have much in common (Konqueror crashes when opened automatically after booting here, not when it's closed like in 156172).

The backtrace looks like the one of bug #162364, it might be a duplicate.

Comment 9 Frank Reininghaus 2008-09-15 19:16:35 UTC

Heinz, can you still reproduce this crash in KDE 4.1 or later? Two bugs which look like duplicates (bug 167227, bug 164998) cannot be reproduced any more and have been closed.

Comment 10 Frank Reininghaus 2008-11-17 22:14:55 UTC

I think this is probably fixed. Heinz, please reopen this report if you get this crash again in KDE 4.1.3 or later. Thanks!

*** This bug has been marked as a duplicate of bug 164998 ***