Bug 380028 - plantage de baloo_file (5.18.0) qui est remplacé aussitot par le même processus avec un nouveau PID
Summary: plantage de baloo_file (5.18.0) qui est remplacé aussitot par le même process...
Status: RESOLVED DUPLICATE of bug 372880
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.18.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-20 09:15 UTC by sournies
Modified: 2018-11-26 20:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
inutile elle parle d'elle même. C'est le 4° rapport, et toujour le même et toujours au démarrage. (2.51 KB, text/plain)
2017-05-20 09:15 UTC, sournies
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sournies 2017-05-20 09:15:55 UTC
Created attachment 105649 [details]
inutile elle parle d'elle même. C'est le 4° rapport, et toujour le même et toujours au démarrage.

bug au démarrage
Application: baloo_file (5.18.0)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-77-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
<Indiquez-nous en détails ce que vous faisiez lors du plantage de l'application.>

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f9ffe40673b in Baloo::IdFilenameDB::get(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#7  0x00007f9ffe41b984 in Baloo::WriteTransaction::replaceDocument(Baloo::Document const&, QFlags<Baloo::DocumentOperation>) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5
#8  0x0000000000429a25 in Baloo::MetadataMover::updateMetadata(Baloo::Transaction*, QString const&, QString const&) ()
#9  0x000000000042a023 in Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) ()
#10 0x00007f9ffdf44baf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x000000000042aaba in KInotify::moved(QString const&, QString const&) ()
#12 0x000000000042cbff in KInotify::slotEvent(int) ()
#13 0x00007f9ffdf44baf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f9ffdfc424e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9ffdf511cb in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f9ffdf1636c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f9ffdf6cc95 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f9ffa507197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f9ffa5073f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f9ffa50749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f9ffdf6c7eb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f9ffdf13b4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f9ffdf1bbec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000000000041698c in main ()
Comment 1 sournies 2017-05-20 09:18:35 UTC
l'ordinateur fonctionne quand même mais c'est génant.
Comment 2 Nate Graham 2018-11-26 20:25:40 UTC

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