Summary: | Dolphin starts to crash all of sudden | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Radosław Mejer <radmen> |
Component: | general | Assignee: | Peter Penz <peter.penz19> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, kyllercg, sam-english, yuri.pugliesi |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Radosław Mejer
2008-08-01 17:25:22 UTC
Can you still reproduce the crash If you start Dolphin in another path? Like "dolphin /" or "dolphin /tmp" or anything other path than your Home folder (may be Dolphin trying to extract info / preview some file within your Home folder do it crash) Naah it's still the same error I have the same problem. Aplicativo: Dolphin (dolphin), sinal SIGABRT [Thread debugging using libthread_db enabled] [New Thread 0x7fc977775780 (LWP 5231)] [KCrash handler] #5 0x00007fc97408def5 in raise () from /lib/libc.so.6 #6 0x00007fc97408f413 in abort () from /lib/libc.so.6 #7 0x00007fc9740ca3e8 in ?? () from /lib/libc.so.6 #8 0x00007fc9740cf968 in ?? () from /lib/libc.so.6 #9 0x00007fc9740d1a76 in free () from /lib/libc.so.6 #10 0x00007fc9744546dd in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 #11 0x00007fc973291487 in std::_List_base<std::pair<std::string, std::string>, std::allocator<std::pair<std::string, std::string> > >::_M_clear () from /usr/lib/libstreamanalyzer.so.0 #12 0x00007fc97328d43c in Strigi::FieldPropertiesDb::Private::parseProperties () from /usr/lib/libstreamanalyzer.so.0 #13 0x00007fc97328d842 in Strigi::FieldPropertiesDb::Private::loadProperties () from /usr/lib/libstreamanalyzer.so.0 #14 0x00007fc973290251 in Strigi::FieldPropertiesDb::Private::Private () from /usr/lib/libstreamanalyzer.so.0 #15 0x00007fc973290f76 in Strigi::FieldPropertiesDb::FieldPropertiesDb () from /usr/lib/libstreamanalyzer.so.0 #16 0x00007fc973290fd4 in Strigi::FieldPropertiesDb::db () from /usr/lib/libstreamanalyzer.so.0 #17 0x00007fc973295815 in Strigi::FieldRegister::registerField () from /usr/lib/libstreamanalyzer.so.0 #18 0x00007fc973295a0a in Strigi::FieldRegister::FieldRegister () from /usr/lib/libstreamanalyzer.so.0 #19 0x00007fc973280e04 in Strigi::AnalyzerConfiguration::AnalyzerConfiguration () from /usr/lib/libstreamanalyzer.so.0 #20 0x00007fc976ea2916 in ?? () from /usr/lib/libkio.so.5 #21 0x00007fc976ea2ad2 in ?? () from /usr/lib/libkio.so.5 #22 0x00007fc976e64e20 in ?? () from /usr/lib/libkio.so.5 #23 0x00007fc976e66edf in KFileMetaInfo::KFileMetaInfo () from /usr/lib/libkio.so.5 #24 0x000000000043efcb in _start () #0 0x00007fc9740fa0b0 in nanosleep () from /lib/libc.so.6 I'm having similar problems. Dolphin just crash without any reason. Sometimes it crashes few seconds after start, sometimes after almost one minute! The backtrace is bellow, But it may not contain anything useful. Aparently it crashes after receiving a SIGABRT signal. I'musing Debian testing (with kde 4.1 unstable packages) \begin{backtrace} Este backtrace parece não ter utilidade. Isto provavelmente ocorre porque seus pacotes foram construídos de uma maneira na qual não podem criar seus próprios backtraces, ou a pilha foi seriamente corrompida. (no debugging symbols found) (no debugging symbols found) (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 0xb5ee2700 (LWP 25075)] 0xb7fb9424 in __kernel_vsyscall () [Current thread is 0 (process 25075)] Thread 1 (Thread 0xb5ee2700 (LWP 25075)): #0 0xb7fb9424 in __kernel_vsyscall () #1 0xb67d9e00 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb67d9c3f in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7b5c678 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? () #0 0xb7fb9424 in __kernel_vsyscall () \end{backtrace} Original bug (comment 0) may be related/duplicate of bug 169103 (ASSERT: "(*it).isValid()") The bug described in comment 3 seems to be another bug. @Yuri Castro Costa Pugliesi, Kyller Gorgonio: Your problem is *not* this one, but bug #169188. As Darío says, the problem is the same as bug #169103. Marking this one as duplicate of #169103 because that bug has more details. *** This bug has been marked as a duplicate of bug 169103 *** too many bugs, too difficult to reinstall a specific component (don't want to uninstall a gui and then have to reinstall it from the command line!) too much techtalk ... how can I recommend using this OS to my boss! is there a more stable reliable filemanager or do I have to tell my boss that MICROSOFT is still our only viable option? Command line is just not acceptable in the 21st century. |