I'm not sure, but I managed to fix the problem about 10 minutes ago by
installing the dependencies required for compiling DT from git. I assumed
that the AUR manager would pull everything in, but I think it didn't and
that might have been the main issue.

I also initially thought it might have been a corrupted XMP file but I
tested that by copying one photo elsewhere without the XMP and importing it
back (after deleting the library.db file), and it still crashed with the
same error.

I don't know how a couple of missing dependencies would produce a ptrace
error but I'm just glad I managed to fix the problem.


On 26 October 2013 13:50, Ulrich Pegelow <ulrich.pege...@tongareva.de>wrote:

> Hi,
>
> you first should allow gdb to generate backtraces. I don't know your
> specific setup but the error message suggests that you may need to
> adjust your system according to this recommendation (see "ptrace
> protection"):
>
>
> https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#ptrace%20Protection
>
>
> Then please try to import images from a "fresh" folder that only
> contains RAWs without any sidecar files. One possible cause of your
> problem might be a corrupted XMP file.
>
> Ulrich
>
>
> Am 26.10.2013 02:04, schrieb Jiew Peng Lim:
> > Hi,
> >
> > Recently I switched from Ubuntu to Manjaro Linux, and I installed
> > darktable-git from the AUR. darktable starts normally. However, if I try
> > to import any image, DT will crash. Subsequently, opening DT will result
> > in almost an instant crash. I can prevent this crash by deleting the
> > library.db file, but DT will crash again upon import. Here's the console
> > output:
> >
> > $ darktable
> > Lua enabled
> > [xmp_import] creating tag: Dual-ISO
> > ptrace: Operation not permitted.
> > /home/<username>/1669: No such file or directory.
> > backtrace written to /tmp/darktable_bt_BET64W.txt
> > Segmentation fault (core dumped)
> >
> > The backtrace file contains the following:
> > this is darktable 1.3+1210~gaa1b42a reporting a segfault:
> >
> > /usr/share/darktable/gdb_commands:2: Error in sourced command file:
> > No stack.
> >
> > I asked about this a while back but the segfault was due to some
> > corrupted images that I had. This time, it crashes regardless of what
> > photos I import.
> >
> > Does anyone know of anything I can do to fix this? Is there any
> > additional info I need to provide?
> >
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> Darktable-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
Darktable-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-users

Reply via email to