Bug 354701 - Dolphin Usage Crash
Summary: Dolphin Usage Crash
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Baloo
Classification: Unmaintained
Component: General (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Vishesh Handa
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-01 18:28 UTC by benjamincolbertsmith
Modified: 2015-12-14 22:49 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
attachment-4583-0.html (2.00 KB, text/html)
2015-11-22 22:31 UTC, benjamincolbertsmith
Details
attachment-4787-0.html (2.47 KB, text/html)
2015-11-22 22:34 UTC, benjamincolbertsmith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description benjamincolbertsmith 2015-11-01 18:28:48 UTC
Application: dolphin (14.12.3)
KDE Platform Version: 4.14.7
Qt Version: 4.8.6
Operating System: Linux 3.19.0-16-generic x86_64
Distribution: Netrunner 16

-- Information about the crash:
I get a crash when I am migrating folders/files around in Dolphin.  It happens with some regularity.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f052bf3a800 (LWP 4363))]

Thread 4 (Thread 0x7f050cb9a700 (LWP 4364)):
#0  0x00007f052b7fa8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f05228eeebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f05228eefcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f052777a82e in operator= (f=..., this=0xa1) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2439
#4  QEventDispatcherGlib::processEvents (this=0x7f05080008e0, flags=<error reading variable: Cannot access memory at address 0x1>) at kernel/qeventdispatcher_glib.cpp:442
#5  0x00007f0527749cd1 in QEventLoop::~QEventLoop (this=0x7f0508003430, __in_chrg=<optimized out>) at kernel/qeventloop.cpp:126
#6  0x00007f0500000024 in ?? ()
#7  0x54668c967a4c4c00 in ?? ()
#8  0x00007f050cb99d70 in ?? ()
#9  0x00007f0508003360 in ?? ()
#10 0x00007f050cb99d80 in ?? ()
#11 0x00007f052774a035 in unlock (this=0x7f050cb99d30) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:119
#12 QEventLoop::exec (this=0x7f050cb99d20, this@entry=0x7f050cb99d80, flags=...) at kernel/qeventloop.cpp:191
#13 0x00007f052763de89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#14 0x00007f052772a443 in QInotifyFileSystemWatcherEngine::run (this=0x7f0508003430) at io/qfilesystemwatcher_inotify.cpp:263
#15 0x000000000000000c in ?? ()
#16 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f0507fff700 (LWP 4365)):
#0  0x00007f0522933789 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f05228eedbd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f05228eefcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f052777a82e in operator= (f=..., this=0xa0) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2439
#4  QEventDispatcherGlib::processEvents (this=0x7f05000008e0, flags=<error reading variable: Cannot access memory at address 0x1>) at kernel/qeventdispatcher_glib.cpp:442
#5  0x00007f0527749cd1 in QEventLoop::~QEventLoop (this=0x7f05000009c0, __in_chrg=<optimized out>) at kernel/qeventloop.cpp:126
#6  0x00007f0500000024 in ?? ()
#7  0x54668c967a4c4c00 in ?? ()
#8  0x00007f0507ffedc0 in ?? ()
#9  0x00007f0500002fa0 in ?? ()
#10 0x00007f0507ffedd0 in ?? ()
#11 0x00007f052774a035 in unlock (this=0x7f0507ffed80) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:119
#12 QEventLoop::exec (this=0x7f0507ffed70, this@entry=0x7f0507ffedd0, flags=...) at kernel/qeventloop.cpp:191
#13 0x00007f052763de89 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#14 0x00007f05276406ff in QThreadPrivate::start (arg=0xfcc220) at thread/qthread_unix.cpp:349
#15 0x00007f0522dd46aa in start_thread (arg=0x7f0507fff700) at pthread_create.c:333
#16 0x00007f052b805eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f050738d700 (LWP 4366)):
#0  0x00007fff229e3c2e in clock_gettime ()
#1  0x00007f052b81438d in __GI___clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:115
#2  0x00007f0527697ac5 in do_gettime (frac=<synthetic pointer>, sec=<synthetic pointer>) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x00007f052777b635 in QTimerInfoList::repairTimersIfNeeded (this=0x7f050738cbb4) at kernel/qeventdispatcher_unix.cpp:418
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f052bf3a800 (LWP 4363)):
[KCrash Handler]
#6  operator= (o=..., this=this@entry=0xffcbb0) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:179
#7  QDateTime::operator= (this=this@entry=0xffcbb0, other=...) at tools/qdatetime.cpp:2200
#8  0x00007f0527b9f768 in KTimeZone::Transition::Transition (this=0x15ab9f0, t=...) at ../../kdecore/date/ktimezone.cpp:256
#9  0x00007f0527ba4951 in node_copy (this=<optimized out>, src=0x16c40d8, to=0x1652bf8, from=<optimized out>) at /usr/include/qt4/QtCore/qlist.h:399
#10 QList<KTimeZone::Transition>::detach_helper (this=<optimized out>, alloc=<optimized out>) at /usr/include/qt4/QtCore/qlist.h:711
#11 0x00007f0527ba23a3 in detach_helper (this=0x1071eb8) at /usr/include/qt4/QtCore/qlist.h:725
#12 detach (this=0x1071eb8) at /usr/include/qt4/QtCore/qlist.h:139
#13 operator[] (i=<optimized out>, this=0x1071eb8) at /usr/include/qt4/QtCore/qlist.h:478
#14 KTimeZoneData::transitionIndex (this=0xdc34c0, dt=..., secondIndex=0x7fff22806c30, validTime=0x7fff22806c1f) at ../../kdecore/date/ktimezone.cpp:1306
#15 0x00007f0527ba2c0c in KTimeZoneBackend::offsetAtZoneTime (this=0x13212f0, caller=0x1568b80, zoneDateTime=..., secondOffset=0x7fff22806cac) at ../../kdecore/date/ktimezone.cpp:516
#16 0x00007f0527b91244 in KDateTimePrivate::timeZoneOffset (this=0x1568b70) at ../../kdecore/date/kdatetime.cpp:606
#17 0x00007f0527b914a8 in KDateTimePrivate::toUtc (this=0x1568b70, local=...) at ../../kdecore/date/kdatetime.cpp:693
#18 0x00007f0527b928e4 in KDateTime::secsTo_long (this=0x7fff22806ed0, t2=...) at ../../kdecore/date/kdatetime.cpp:1188
#19 0x00007f0527b92b19 in KDateTime::secsTo (this=<optimized out>, t2=...) at ../../kdecore/date/kdatetime.cpp:1161
#20 0x00007f0527c823ed in KLocalePrivate::formatDateTime (this=0xcdb150, dateTime=..., format=22605825, options=...) at ../../kdecore/localization/klocale_kde.cpp:2570
#21 0x00007f0527c7d654 in KLocale::formatDateTime (this=<optimized out>, dateTime=..., format=format@entry=KLocale::FancyLongDate, options=...) at ../../kdecore/localization/klocale.cpp:463
#22 0x00007f0529c4246b in Baloo::FileMetaDataProvider::Private::insertBasicData (this=this@entry=0x1009690) at ../../src/filemetadataprovider.cpp:295
#23 0x00007f0529c429d2 in Baloo::FileMetaDataProvider::Private::slotLoadingFinished (this=0x1009690, job=<optimized out>) at ../../src/filemetadataprovider.cpp:270
#24 0x00007f052776019c in QMetaObject::activate (sender=sender@entry=0x1620470, m=m@entry=0x7f0527f82f20 <KJob::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff22807270) at kernel/qobject.cpp:3560
#25 0x00007f0527be10bf in KJob::finished (this=this@entry=0x1620470, _t1=_t1@entry=0x1620470) at ./kjob.moc:186
#26 0x00007f0527be13b5 in KJob::emitResult (this=this@entry=0x1620470) at ../../kdecore/jobs/kjob.cpp:316
#27 0x00007f0529c4595e in Baloo::IndexedDataRetriever::slotIndexedFile (this=0x1620470) at ../../src/indexeddataretriever.cpp:65
#28 0x00007f052776019c in QMetaObject::activate (sender=sender@entry=0xc62d30, m=m@entry=0x7f0527aad280 <QProcess::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff22807430) at kernel/qobject.cpp:3560
#29 0x00007f05276d8301 in QProcess::finished (this=this@entry=0xc62d30, _t1=1) at .moc/release-shared/moc_qprocess.cpp:148
#30 0x00007f05276dc93e in QProcessPrivate::_q_processDied (this=0x1620590) at io/qprocess.cpp:1088
#31 0x00007f05276dc9b9 in QProcess::qt_static_metacall (_o=0xffcbb0, _id=17499040, _a=0x7f0527ab3901 <qDetectCPUFeatures()::features+1>, _c=<optimized out>) at .moc/release-shared/moc_qprocess.cpp:91
#32 0x00007f052776019c in QMetaObject::activate (sender=0x1166ba0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff228075c0) at kernel/qobject.cpp:3560
#33 0x00007f05277ad4fe in ?? () at .moc/release-shared/moc_qmimedata.cpp:71 from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#34 0x0000000000000003 in ?? ()
#35 0x0000001f7a4c4c00 in ?? ()
#36 0x0000000000000000 in ?? ()

The reporter indicates this bug may be a duplicate of or related to bug 302449.

Possible duplicates by query: bug 302449.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2015-11-22 18:24:57 UTC
Thanks for the bug report. This looks like a Baloo issue, since you are using the kdelibs 4.x-based Dolphin, you are probably using a rather outdated Baloo version. It would be interesting to know if the crash can also be reproduced with more recent versions.
Comment 2 benjamincolbertsmith 2015-11-22 22:31:03 UTC
Created attachment 95660 [details]
attachment-4583-0.html

Hi Frank, I am no longer using Dolphin.  Thanks for looking into it
though.  If I do indeed reproduce the error with different settings I the
future, I will write you back.
On Nov 22, 2015 12:25 PM, "Frank Reininghaus via KDE Bugzilla" <
bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=354701
>
> Frank Reininghaus <frank78ac@googlemail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |frank78ac@googlemail.com,
>                    |                            |pinak.ahuja@gmail.com
>           Component|general                     |General
>             Product|dolphin                     |Baloo
>            Assignee|dolphin-bugs-null@kde.org   |me@vhanda.in
>
> --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> ---
> Thanks for the bug report. This looks like a Baloo issue, since you are
> using
> the kdelibs 4.x-based Dolphin, you are probably using a rather outdated
> Baloo
> version. It would be interesting to know if the crash can also be
> reproduced
> with more recent versions.
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 3 benjamincolbertsmith 2015-11-22 22:34:53 UTC
Created attachment 95662 [details]
attachment-4787-0.html

No longer using Kde, as well as dolphin.
On Nov 22, 2015 4:30 PM, "Ben Smith" <benjamincolbertsmith@gmail.com> wrote:

> Hi Frank, I am no longer using Dolphin.  Thanks for looking into it
> though.  If I do indeed reproduce the error with different settings I the
> future, I will write you back.
> On Nov 22, 2015 12:25 PM, "Frank Reininghaus via KDE Bugzilla" <
> bugzilla_noreply@kde.org> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=354701
>>
>> Frank Reininghaus <frank78ac@googlemail.com> changed:
>>
>>            What    |Removed                     |Added
>>
>> ----------------------------------------------------------------------------
>>                  CC|                            |frank78ac@googlemail.com
>> ,
>>                    |                            |pinak.ahuja@gmail.com
>>           Component|general                     |General
>>             Product|dolphin                     |Baloo
>>            Assignee|dolphin-bugs-null@kde.org   |me@vhanda.in
>>
>> --- Comment #1 from Frank Reininghaus <frank78ac@googlemail.com> ---
>> Thanks for the bug report. This looks like a Baloo issue, since you are
>> using
>> the kdelibs 4.x-based Dolphin, you are probably using a rather outdated
>> Baloo
>> version. It would be interesting to know if the crash can also be
>> reproduced
>> with more recent versions.
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>>
>
Comment 4 Frank Reininghaus 2015-11-23 20:16:50 UTC
Thanks for the quick reply. I'll close the report then because Baloo and the date/time code where the crash happens have changed quite a lot recently, and it's possible that this problem does not exist any more (i am not aware of any recent reports with this backtrace).

If you do see the problem again with Dolphin 15.08.x or later, please reopen this report or file a new one. Thanks for your help!
Comment 5 Vishesh Handa 2015-12-14 22:49:55 UTC
Sorry. Baloo Qt4 is no longer maintained. Please upgrade.