Opened 11 years ago
Last modified 11 years ago
#41659 new defect
digikam crash-Very unstable
| Reported by: | gtmdhl@… | Owned by: | jgosmann (Jan Gosmann) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.1 |
| Keywords: | Cc: | cgilles (HumanDynamo) | |
| Port: | digikam |
Description
Imac running OS 10.9 with Xcode 5.0.2, Xcode Command Line Tools extension package for Maverick, MacPort, and digikam (3.5.0). I am unsophisticated regarding the language of Open Source but was successful in getting all the items installed to open Digikam. However, when it opens it is very unstable and crashes upon any simple attempt to run any menu items. Please review the load log, attached. I would appreciate any guidance to resolve the crash syndrome as I support Open Source and would enjoy using Digikam. Thank you, David Lyon
Attachments (1)
Change History (9)
Changed 11 years ago by gtmdhl@…
| Attachment: | digikam load journal file.rtf added |
|---|
comment:1 Changed 11 years ago by mf2k (Frank Schima)
| Cc: | caulier.gilles@… added |
|---|---|
| Keywords: | Crash removed |
| Owner: | changed from macports-tickets@… to jan@… |
| Port: | digikam added; digiskam removed |
In the future, please Cc the port maintainers (port info --maintainers digikam).
comment:2 follow-up: 3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
If digikam crashes, please attach the crash log from ~/Library/Logs/DiagnosticReports.
comment:3 Changed 11 years ago by gtmdhl@…
Replying to ryandesign@…:
If digikam crashes, please attach the crash log from ~/Library/Logs/DiagnosticReports.
Using the suggested nomenclature suggested (bash-3.2$ ~/Library/Logs/DiagnosticReports) I receive
bash: /Users/David/Library/Logs/DiagnosticReports: is a directory bash-3.2$
comment:4 follow-up: 5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Yes, ~/Library/Logs/DiagnosticReports is a directory. Whenever a program crashes, the OS writes a crash log into that directory. Please check if any of the crash logs in that directory mention digikam; if so, please attach the most recent one.
comment:5 follow-up: 6 Changed 11 years ago by gtmdhl@…
Replying to ryandesign@…:
Yes, ~/Library/Logs/DiagnosticReports is a directory. Whenever a program crashes, the OS writes a crash log into that directory. Please check if any of the crash logs in that directory mention digikam; if so, please attach the most recent one.
Please forgive my ignorance but if you could instruct me how to open an directory, i could provide the requested information. david
comment:6 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to gtmdhl@…:
Replying to ryandesign@…:
Yes, ~/Library/Logs/DiagnosticReports is a directory. Whenever a program crashes, the OS writes a crash log into that directory. Please check if any of the crash logs in that directory mention digikam; if so, please attach the most recent one.
Please forgive my ignorance but if you could instruct me how to open an directory, i could provide the requested information.
One method: in the Finder, select "Go to Folder" from the "Go" menu, type (or paste) "~/Library/Logs/DiagnosticReports" and press Return or click OK.
Another method: in a Terminal window, type (or paste):
open ~/Library/Logs/DiagnosticReports
and press Return.
comment:7 Changed 11 years ago by jgosmann (Jan Gosmann)
This might be a related to or a duplicate of #41709.
Unfortunately, I do not have much time to look into it right now.
comment:8 Changed 11 years ago by jgosmann (Jan Gosmann)
Finally looked at the load log, but it doesn't contain any information which is helpful to me. My install of digikam seems stable so that I cannot reproduce the problem.
But from the problem description I believe it is a duplicato of #41709 as mentioned before. Try running digikam with DYLD_PRINT_LIBRARIES=1 /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam as suggested there. Uninstalling and reinstalling Qt4 and Digikam might also help.
digikam load log