| Summary: | crash when run from sudo | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Maciej Pilichowski <bluedzins> |
| Component: | kcm_kdm | Assignee: | kdm bugs tracker <kdm-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Maciej Pilichowski
2008-08-29 16:53:02 UTC
the backtrace is halfways useless. try running systemsettings in a proper root shell (started with sux), directly in gdb if you do not get a proper kde crash report. anyway, the trace indicates that the crash is in strigi. preferably, upgrade it and if it is still crashing, file a bug with strigi. Oswald, I would like to help but I can't. systemsettings won't run after su, I can run it only after sudo (probably something wrong with X display rights) I don't see systemsettings-dbg companion package (well, I am new to debian) running what I have from gdb produced very similar trace which part of "started with sux" exactly don't you understand? I missed x, irony is not needed. It does not work either, after run in gdb I get error Cannot find the D-Bus session server so even systemsettings is not started. maybe try "sux -"? Thanks, it worked. KDECrashHandler: Application: System Settings (systemsettings), signal SIGABRT (no debugging symbols found) 0xb7f73416 in __kernel_vsyscall () [Current thread is 0 (LWP 2524)] Thread 2 (Thread 0xb4824b90 (LWP 2531)): #0 0xb7f73416 in __kernel_vsyscall () #1 0xb6a85b71 in select () from /lib/i686/cmov/libc.so.6 #2 0xb6d1d180 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb6c4e4a2 in ?? () from /usr/lib/libQtCore.so.4 #4 0xb64ea510 in start_thread () from /lib/i686/cmov/libpthread.so.0 #5 0xb6a8d79e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb60dea30 (LWP 2524)): #0 0xb7f73416 in __kernel_vsyscall () #1 0xb6a48d56 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb6a48b6f in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7dea678 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? () #0 0xb7f73416 in __kernel_vsyscall () Is this trace useful? > Is this trace useful?
>
not at all ... it says "current thread 0", but there is no backtrace from thread 0 ... if this is really all you get from the crash dialog, you should start it directly in gdb and create a backtrace manually once it crashes.
Directly Login Manager? What is the name of the executable? systemsettings, of course, as this is what crashes. but you should try "kcmshell4 kdm", too - if that does not crash, i can get rid of the report. :) You mean gdb systemsettings run ? I did it already. Otherwise I wouldn't get any backtrace in kde crash handler. Bad news ;-) kcmshell4 kde crashes as well. > gdb systemsettings > > I did it already. Otherwise I wouldn't get any backtrace in kde crash handler. > oh. try gdb --args kcmshell4 kdm run but i somehow don't think this will be much different ... mind figuring out how to get a backtrace of the actually crashing thread 0? > Bad news ;-) kcmshell4 kde crashes as well. > tough luck. :} The first part looks a bit different, I paste it at the end.
> mind figuring out how to get a backtrace of the actually crashing thread 0?
If you ask me, well, I don't know anything about gdb really.
======= Backtrace: =========
/lib/i686/cmov/libc.so.6[0xb7eb8234]
/lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7eba296]
/usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb6cb7281]
/usr/lib/libstdc++.so.6(_ZdaPv+0x1d)[0xb6cb72dd]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi17FieldPropertiesDb7Private15parsePropertiesEPc+0x1c2)[0xb640e882]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi17FieldPropertiesDb7Private14loadPropertiesERKSs+0x28e)[0xb640ecbe]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi17FieldPropertiesDb7PrivateC1Ev+0xc54)[0xb64114e4]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi17FieldPropertiesDbC1Ev+0x30)[0xb64122a0]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi17FieldPropertiesDb2dbEv+0x52)[0xb6412322]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi13FieldRegister13registerFieldERKSs+0x105)[0xb6419205]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi13FieldRegisterC1Ev+0x47)[0xb6419457]
/usr/lib/libstreamanalyzer.so.0(_ZN6Strigi21AnalyzerConfigurationC2Ev+0x7f)[0xb6402bbf]
/usr/lib/libkio.so.5[0xb6aa395d]
/usr/lib/libkio.so.5[0xb6aa3b7b]
/usr/lib/libkio.so.5[0xb6a61404]
/usr/lib/libkio.so.5(_ZN13KFileMetaInfoC1ERK7QStringS2_6QFlagsINS_4WhatEE+0x1a5)[0xb6a631f5]
/usr/lib/kde4/kcm_kdm.so[0xb4969c75]
/usr/lib/kde4/kcm_kdm.so[0xb496c151]
/usr/lib/kde4/kcm_kdm.so[0xb496e52f]
/usr/lib/kde4/kcm_kdm.so[0xb4989543]
/usr/lib/kde4/kcm_kdm.so[0xb49a8482]
/usr/lib/kde4/kcm_kdm.so(_ZN14KPluginFactory14createInstanceI8KDModule7QWidgetEEP7QObjectPS2_S4_RK5QListI8QVariantE+0x71)[0xb49ac8b1]
/usr/lib/libkdecore.so.5(_ZN14KPluginFactory6createEPKcP7QWidgetP7QObjectRK5QListI8QVariantERK7QString+0x2d7)[0xb7dc2387]
/usr/lib/libkutils.so.4(_ZN8KService14createInstanceI8KCModuleEEPT_RK10KSharedPtrIS_EP7QObjectRK5QListI8QVariantEP7QString+0xa6)[0xb7e18436]
/usr/lib/libkutils.so.4(_ZN14KCModuleLoader10loadModuleERK12KCModuleInfoNS_14ErrorReportingEP7QWidgetRK11QStringList+0x1e2)[0xb7e172a2]
/usr/lib/libkutils.so.4[0xb7e1d63d]
/usr/lib/libkutils.so.4(_ZNK13KCModuleProxy10realModuleEv+0x63)[0xb7e1e763]
/usr/lib/libkutils.so.4(_ZNK13KCModuleProxy15minimumSizeHintEv+0x28)[0xb7e1e798]
/usr/lib/libkdeui.so.5[0xb7188fe3]
/usr/lib/libkdeui.so.5(_ZN9KPageView11qt_metacallEN11QMetaObject4CallEiPPv+0x14e)[0xb718919e]
/usr/lib/libkdeui.so.5(_ZN11KPageWidget11qt_metacallEN11QMetaObject4CallEiPPv+0x3a)[0xb718ce8a]
/usr/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x200)[0xb6e48830]
/usr/lib/libQtCore.so.4(_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+0x52)[0xb6e495b2]
/usr/lib/libQtCore.so.4(_ZN18QAbstractItemModel13layoutChangedEv+0x37)[0xb6e82817]
/usr/lib/libkdeui.so.5(_ZN16KPageWidgetModel7addPageEP15KPageWidgetItem+0xc4)[0xb718f824]
/usr/lib/libkdeui.so.5(_ZN11KPageWidget7addPageEP15KPageWidgetItem+0x2a)[0xb718d13a]
/usr/lib/libkdeui.so.5(_ZN11KPageDialog7addPageEP15KPageWidgetItem+0x2a)[0xb718666a]
/usr/lib/libkutils.so.4(_ZN13KCMultiDialog9addModuleERK12KCModuleInfoP15KPageWidgetItemRK11QStringList+0xcbc)[0xb7e19ebc]
/usr/lib/libkdeinit4_kcmshell4.so(kdemain+0x1419)[0xb7fad8f9]
kcmshell4[0x8048592]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7e5f685]
kcmshell4[0x80484d1]
looks the same for all practical purposes. anyway, assuming you *do* have the latest version of strigi by now, run "valgrind --num-callers=50 --log-file=kcm_kdm-log kcmshell4 kdm", wait quite a bit and attach the resulting log. Your problem has nothing to do with systemsettings, kdm or kcmshell4. *** This bug has been marked as a duplicate of bug 169188 *** |