Digikam segfaults with "Address not mapped to object"

T

tOsYZYny

I had run an older version of digikam in the past (on a dedicated system, not in a jail) with no issues, but am presently running 8.1.0 and getting segfaults just opening the application. Upon looking at the error message (with the help of gdb), I figured that ASLR might be to blame, so I had disabled that. I got a little bit further and was able to load an image, but then it crashed again with the exact same error. When I set the sysctls, I stopped and restarted the jail.

gdb -c digikam.core

Code: 
[New LWP 552309]
[New LWP 544273]
[New LWP 552306]
[New LWP 552307]
[New LWP 552308]
[New LWP 552310]
[New LWP 552343]
[New LWP 552344]
[New LWP 552345]
[New LWP 552346]
[New LWP 552347]
[New LWP 552348]
[New LWP 552349]
[New LWP 552351]
[New LWP 552352]
[New LWP 552353]
[New LWP 552354]
[New LWP 552355]
[New LWP 552356]
[New LWP 552357]
[New LWP 552358]
[New LWP 552359]
[New LWP 552360]
[New LWP 552363]
[New LWP 552364]
[New LWP 552367]
[New LWP 552368]
[New LWP 552369]
[New LWP 552370]
[New LWP 552371]
[New LWP 552389]
[New LWP 552390]
[New LWP 552391]
[New LWP 552392]
[New LWP 552393]
Core was generated by `digikam'.
Program terminated with signal SIGSEGV, Segmentation fault.
Address not mapped to object.
#0  0x00000008044077b4 in ?? ()
[Current thread is 1 (LWP 552309)]

I am running digikam in a jail and for reference, all of my other X11 stuff seems to work fine. I'm not sure if it is jail-related or what.

Any ideas? I shouldn't have to restart the host to completely disable ASLR, right? I've had issues in the past with some go applications and merely relaunching those after changing the sysctl allowed those to run just fine.
 
Last edited:
I have since upgraded to FreeBSD 14 (fresh install) and am running into the same problem.

Code: 
[New LWP 145995]
[New LWP 145964]
[New LWP 145992]
[New LWP 145993]
[New LWP 145994]
[New LWP 145996]
[New LWP 145998]
[New LWP 145999]
[New LWP 146000]
[New LWP 146001]
[New LWP 146002]
[New LWP 146003]
[New LWP 146004]
[New LWP 146006]
[New LWP 146007]
[New LWP 146008]
[New LWP 146009]
[New LWP 146010]
[New LWP 146011]
[New LWP 146012]
[New LWP 146013]
[New LWP 146014]
[New LWP 146015]
[New LWP 146018]
[New LWP 146019]
[New LWP 146022]
[New LWP 146023]
[New LWP 146024]
[New LWP 146025]
[New LWP 146042]
--Type <RET> for more, q to quit, c to continue without paging--
[New LWP 146043]
[New LWP 146044]
[New LWP 146045]
[New LWP 146046]
Core was generated by `digikam'.
Program terminated with signal SIGSEGV, Segmentation fault.
Address not mapped to object.

Is anyone else having this issue or just me? I am running digikam in a jail and prior to that, it did work fine.
 
FWIW, I use digikam now and again (not in a Jail) and have not experienced any problems. FreeBSD 14.0. digikam 8.2.0_1 from quarterly packages.
 
Thanks for sharing, so it must be something on my end.

I just reverted back to using it outside of a jail and it still segfaults for me. I am trying to import my collection which is about 300G of images and videos, and would imagine digikam can handle as many images and videos as you want to throw at it. I don't believe the digikam database files were corrupt because I think I started anew anyways, but will check that again.
 
After clearing out my digikam database files and trying anew:

[New LWP 117916]
[New LWP 100955]
[New LWP 117914]
[New LWP 117915]
[New LWP 117917]
[New LWP 117936]
[New LWP 117938]
[New LWP 117939]
[New LWP 117940]
[New LWP 118858]
[New LWP 118859]
[New LWP 118860]
[New LWP 118861]
[New LWP 118863]
[New LWP 118864]
[New LWP 118865]
[New LWP 118868]
[New LWP 118869]
[New LWP 118870]
[New LWP 118871]
[New LWP 118874]
[New LWP 118875]
[New LWP 118878]
[New LWP 118880]
[New LWP 118881]
[New LWP 118902]
[New LWP 118903]
[New LWP 118904]
[New LWP 118905]
[New LWP 118906]
--Type <RET> for more, q to quit, c to continue without paging--
Core was generated by `digikam'.
Program terminated with signal SIGSEGV, Segmentation fault.
Address not mapped to object.
#0 0x00000008043c5064 in ?? ()
[Current thread is 1 (LWP 117916)]
Click to expand...

Prior to that, there were some errors trying to read a gimp file.

I am using git annex to manage my files if that makes any difference (all files end up getting stored under .git and the original files are replaced with symlinks). I don't believe it should, but perhaps it does.
 
I am trying to run digikam 8.2.0 on FreeBSD 14 p5 and still getting segfaults. I have disabled aslr settings, but it still segfaults. It produces the same output as earlier, address not mapped to object. By disabling, I have set all aslr settings off and restarted digikam, but it still segfaults.

Are you doing anything in particular? Do you have any suggestions?

I shouldn't need to reboot with the ASLR settings disabled, correct?
 
Sorry, can't offer any advice. It just works for me - it's a completely stock installation. Just updated to 14.0-RELEASE-p5 and digikam 8.2.0_2 and everything still OK. The PC is 10+ years old so no issues with new hardware compatibility.
 
Ok, I too am on hardware that is 10+ years old :). I changed my aslr settings in my /boot/loader.conf and rebooted, but still encountered a segfault. This is the output when running digikam from a console:

Code: 
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
kf.sonnet.core: No language dictionaries for the language: "en_US"
zsh: segmentation fault (core dumped)  digikam

I am wondering if that perhaps it is related to the dictionary / language message?
 
Here's my working console output:

Code: 
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected"
 "Not connected to D-Bus server"
kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected"
 "Not connected to D-Bus server"
kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected"
 "Not connected to D-Bus server"
kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected"
 "Not connected to D-Bus server"
digikam.metaengine: ExifTool process cannot be started ( "" )
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected"
 "Not connected to D-Bus server"
kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected"
 "Not connected to D-Bus server"
kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
 
Lots of those messages are just useless noise that the developer should only output with a "verbose" option.

[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1)
Click to expand...

That one looks fairly bad.

From your gdb loading the core does 'backtrace' give anything useful?
Can you run digikam in gdb?
 
Running 'backtrace' doesn't produce anything useful, I'm running the stock version of digikam and I suppose I need to build it with debug symbols to get something useful. I tried building digikam, but haven't got the patience to build and replace a bunch of stock programs. The only other possibility is that I still see some ASLR settings set to 1 even though I didn't set them in my loader.conf. I will explicitly set those to 0, reboot and test. Setting those via sysctl and rerunning digikam didn't change anything.
 
You must log in or register to reply here.
Back
Top