Summary: | kmahjongg crashes when use custom layout | ||
---|---|---|---|
Product: | [Applications] kmahjongg | Reporter: | Oleg Kukharchuk <oleg.kuh> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kde-games-bugs, msp |
Priority: | NOR | Keywords: | drkonqi |
Version: | 0.8 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | layout file |
Description
Oleg Kukharchuk
2013-11-08 23:01:15 UTC
Created attachment 83435 [details]
layout file
*** This bug has been marked as a duplicate of bug 322518 *** *** This bug has been marked as a duplicate of bug 188413 *** Control: forward -1 https://bugs.kde.org/show_bug.cgi?id=327377 Control: severity -1 important On Sat, 9 Nov 2013 15:53:04 Rainer Dorsch wrote: > Upgrade: digikam-private-libs:i386 (3.4.0-1, 3.5.0-2), digikam:i386 > (3.4.0-1, 3.5.0-2), digikam-data:i386 (3.4.0-1, 3.5.0-2) Rainer, I see you have also filed a report with upstream, so have noted the Debian bug as forwarded. There has been very little change between your upgraded versions (3.4 -> 3.5), as this was a maintenance release, I believe 5 bugs were fixed: https://bugs.kde.org/buglist.cgi?f1=cf_versionfixedin&o1=equals&query_format=advanced&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&v1=3.5.0&product=digikam&product=digikamimageplugins&product=kipiplugins&product=showfoto There have also been no other reports of albums disappearing, although 3.5 has been available since 10 October, so I have set the severity of your report to important. I would imagine it has to do with the location of your digikam4.db file, is that located in your Pictures directory and have you changed this? I would recommend you check the quality of these databases, especially your backup before you used digikam/3.5: http://userbase.kde.org/Digikam/Check_Database Your tags can also be located in digikam4.db, unless you choose to store them in each picture file. I'll let the digikam team provide you some further assistance via 327337. Mark Mark, comment #4 was added to the wrong bug report. Can you check the forwarding? |