Bug 166231

Summary:	When starting File Manager - Superuser Mode from the Kmenu (konqueror --profile filemanagement) konqueror crashes (signal 11 SIGSEGV)
Product:	[Applications] konqueror	Reporter:	Rik <rfe.gen>
Component:	general	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	frank78ac
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rik 2008-07-10 15:18:49 UTC

Version:           4.0.5 (KDE 4.0.5) (using 4.0.5 (KDE 4.0.5), 4.0.5-5.fc9 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.25.9-76.fc9.x86_64

When starting File Manager - Superuser Mode from the Kmenu (konqueror --profile filemanagement) konqueror crashes (signal 11 SIGSEGV)
Strange thing is that I can start konqueror in superuser mode without problems when I use a console and type su - pwd konqueror
I tried removing /root/.kde/share/config/konquerorrc but that dit not solve the problem.

This is the output of the crash handler...
[?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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0x7f4a14b5d7e0 (LWP 14962)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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]
#5  0x000000329606e63b in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#6  0x000000329608db4d in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#7  0x0000003293afc3a6 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#8  0x00007f4a0d6e6e10 in ?? () from /usr/lib64/kde4/dolphinpart.so
#9  0x0000003293afc3a6 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#10 0x00007f4a0d4c2963 in DolphinView::applyViewProperties ()
   from /usr/lib64/libdolphinprivate.so.4
#11 0x00007f4a0d4c41b3 in DolphinView::updateView ()
   from /usr/lib64/libdolphinprivate.so.4
#12 0x00007f4a0d4c425f in DolphinView::setUrl ()
   from /usr/lib64/libdolphinprivate.so.4
#13 0x00007f4a0d6e5c83 in ?? () from /usr/lib64/kde4/dolphinpart.so
#14 0x0000003296041bc1 in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#15 0x000000329607c895 in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#16 0x0000003296048926 in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#17 0x00000032960477fc in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#18 0x00000032960474bd in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#19 0x0000003296048b5c in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#20 0x0000003296049b38 in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#21 0x000000329604a05a in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#22 0x000000329604cca1 in ?? () from /usr/lib64/libkdeinit4_konqueror.so
#23 0x00000032960aa148 in kdemain () from /usr/lib64/libkdeinit4_konqueror.so
#24 0x00000036f661e32a in __libc_start_main () from /lib64/libc.so.6
#25 0x0000000000400809 in _start ()

Comment 1 Christophe Marin 2008-07-10 17:59:42 UTC

Please read the following page and provide a useful backtrace for this crash : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 2 Frank Reininghaus 2008-07-10 18:55:19 UTC

Thanks for the bug report. This looks very similar to a bug reported earlier, so I'm marking this as a duplicate (feel free to reopen if I'm wrong).

If you can provide a better backtrace, please paste it in the other report.

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