| Summary: | digiKam crash while tagging photos (Baloo database) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Heikki <heikki> |
| Component: | Database-Baloo | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | burdickjp, caulier.gilles, chabot.daniel, ddgreen, k, me, pierre_metzner, veaceslav.munteanu90 |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Heikki
2014-11-13 18:09:50 UTC
It crash in Baloo. Veaceslav, this entry must be moved to Baloo bugzilla section ? Gilles After doing the following I have experienced no crashes while tagging the photos for more than two hours. Much longer than yesterday. Some days ago the digikam crashed while starting. I got from the web some indication that the reason may be do to videos I have in the album. Just as a guess I changed priority of my packman repository to 101 and the priority of KDE-Extra to 100. ( I have understood that it is not adviced.) Surprisingly the digikam started to work except the crashes I experienced yesterday. Today I changed all the priorities to 99 and installed the latest updates of tumbleweed with the command zypper dup. There has been no crashes for quite a long time after that. (Yesterday I started my system from suspend to RAM state, today I rebooted the system after the update. I have got a feeling that sometimes something does not work properly after suspend, but that is just a feeling based on no evidence or facts. Nonsense I guess.) I will report if I experience a crash. *** Bug 342489 has been marked as a duplicate of this bug. *** *** Bug 342760 has been marked as a duplicate of this bug. *** The crash appear in sqlite database managed by Baloo. See trace from bug #342760. Problem is located in Baloo file management implementation, not digiKam Gilles Caulier *** Bug 343066 has been marked as a duplicate of this bug. *** When implementing baloo syncronization, I also added some switches in digiKam options. Just switch baloo off in metadata tab, until the problem is fixed. Fixed Baloo in Qt5. Baloo-Qt4 is no longer getting any more updates. Thanks Vishesh, I report this info to future digiKam for KF5 under development. Gilles Caulier *** Bug 347915 has been marked as a duplicate of this bug. *** Created attachment 98520 [details]
New crash information added by DrKonqi
digikam (4.14.0) on KDE Platform 4.14.16 using Qt 4.8.7
- What I was doing when the application crashed:
I add a Tag to a Photho, the digikam crashes
-- Backtrace (Reduced):
#6 0x00007fbf84c84435 in Xapian::Database::get_document (this=0x0, did=did@entry=252) at ../api/omdatabase.cc:440
#7 0x00007fbf84a3a6b4 in Baloo::XapianDatabase::document (this=0x7fbf1c07da10, id=252) at ../../../src/xapian/xapiandatabase.cpp:159
#8 0x00007fbf8e8beef7 in Baloo::FileModifyJob::doStart (this=0x7fbf1c020110) at ../../../../src/file/lib/filemodifyjob.cpp:144
#9 0x00007fbf92633db1 in QObject::event (this=0x7fbf1c020110, e=<optimized out>) at kernel/qobject.cpp:1222
#10 0x00007fbf93029fdc in QApplicationPrivate::notify_helper (this=this@entry=0x29a9db0, receiver=receiver@entry=0x7fbf1c020110, e=e@entry=0x7fbf1c0219a0) at kernel/qapplication.cpp:4570
|