Summary: | Nepomuk baloo migration can't seem to access the database | ||
---|---|---|---|
Product: | [Unmaintained] Baloo | Reporter: | J. "TAKUMI" Burton <sougonnatakumi> |
Component: | General | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | crash | CC: | alexo.veto, cfeck, peter, rz, yehielb |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
J. "TAKUMI" Burton
2014-04-18 07:41:59 UTC
*** Bug 334439 has been marked as a duplicate of this bug. *** *** Bug 337150 has been marked as a duplicate of this bug. *** *** Bug 338181 has been marked as a duplicate of this bug. *** I set: ulimit -n 900000 and tried again - it is imported some metadata, but then import is seems to be stopped with the messages like that: nepomukbaloomigrator(6610) Nepomuk2::SysTray::startMigration: "/home/pictures/screenshots/umplayer/shot0133.png" 0 "" ("HunterD") nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610) Baloo::XapianDatabase::commit: Adding: 1 docs nepomukbaloomigrator(6610) Baloo::XapianDatabase::commit: Removing: 0 docs nepomukbaloomigrator(6610) Baloo::XapianDatabase::commit: Xapian Committed nepomukbaloomigrator(6610) Nepomuk2::SysTray::startMigration: "/home/pictures/screenshots/umplayer/shot0119.png" 0 "" ("HunterxHunter") nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610): "database is locked Unable to fetch row" nepomukbaloomigrator(6610) Baloo::XapianDatabase::commit: Adding: 1 docs nepomukbaloomigrator(6610) Baloo::XapianDatabase::commit: Removing: 0 docs nepomukbaloomigrator(6610) Baloo::XapianDatabase::commit: Xapian Committed After i set: ulimit -n 900000 it stop crashing and successfully migrated most(or at least a big part) of metadata, but where was a plenty of files which metadata still didn't migrated if message: nepomukbaloomigrator(6610): "database is locked Unable to fetch row" appeared 1 time - metadata migrated, but if it appeared 4 times - migration failed Hey guys. I'm sorry, but I'm going to be marking this BUG as WONTFIX. It's not that the crash isn't important, it's just that reproducing it is quite hard. Additionally the underlying code has changed quite a bit between Baloo from Qt4 and Qt5. Considering that the Nepomuk-Baloo migrator required Nepomuk, which has not been ported to Qt5, and will probably never be. The migrator no longer exists in Qt5. *** Bug 342812 has been marked as a duplicate of this bug. *** My best workaround so far: # some really big number vim /etc/security/limits.conf balooctl stop; ulimit -S -n 100000; rm ~/.kde/share/config/nepomukserverrc; nepomukctl start; sleep 600; nepomukbaloomigrator #- and try that a few times |