Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#52787 - [darktable] Segfaults with 2:2.2.2-1

Attached to Project: Community Packages
Opened by Stephan Munsch (forest_bear59) - Tuesday, 31 January 2017, 09:59 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 07 February 2017, 19:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The new Darktable version 2:2.2.2-1 yields a segfault after some ttime when working with a RAW file. I have experienced this problem with DNG files from a Pentax K20D. First there is a message that this camera could not be found in the database. But the version 2:2.2.1-1 did not complain so. When opening a RAW (DNG) file, the applicaton crashes within some time, sometimes even when no further action have been made.


Steps to reproduce:

have been wirtten before.

Here is a terminal protocol:

[defaults] found a 64-bit system with 16321280 kb ram and 8 cores (0 atom based)
[defaults] setting high quality defaults

(darktable:17394): Gtk-WARNING **: Failed to measure available space: Der angegebene Ort wird nicht unterstützt
RawSpeed:Unable to find camera in database: 'PENTAX' 'PENTAX K20D' 'dng'
Please consider providing samples on <https://raw.pixls.us/>, thanks!
[New LWP 17395]
[New LWP 17396]
[New LWP 17417]
[New LWP 17418]
[New LWP 17419]
[New LWP 17420]
[New LWP 17421]
[New LWP 17422]
[New LWP 17423]
[New LWP 17424]
[New LWP 17425]
[New LWP 17426]
[New LWP 17427]
[New LWP 17436]
[New LWP 17439]
[New LWP 17593]
[New LWP 18074]
[New LWP 18075]
[New LWP 18076]
[New LWP 18077]
[New LWP 18078]
[New LWP 18079]
[New LWP 18080]
[New LWP 18081]
[New LWP 18082]
[New LWP 18083]
[New LWP 18084]
[New LWP 18085]
[New LWP 18086]
[New LWP 18087]
[New LWP 18088]
[New LWP 18089]
[New LWP 18090]
[New LWP 18091]
[New LWP 18092]
[New LWP 18093]
[New LWP 18094]
[New LWP 18115]
[New LWP 18116]
[New LWP 18117]
[New LWP 18118]
[New LWP 18119]
[New LWP 18120]
[New LWP 18121]
[New LWP 18122]
[New LWP 18123]
[New LWP 18124]
[New LWP 18125]
[New LWP 18126]
[New LWP 18127]
[New LWP 18128]
[New LWP 18129]
[New LWP 18130]
[New LWP 18131]
[New LWP 18132]
[New LWP 18133]
[New LWP 18134]
[New LWP 18135]
[New LWP 18136]
[New LWP 18137]
[New LWP 18138]
[New LWP 18139]
[New LWP 18140]
[New LWP 18141]
[New LWP 18142]
[New LWP 18203]
[New LWP 18204]
[New LWP 18205]
[New LWP 18206]
[New LWP 18207]
[New LWP 18208]
[New LWP 18209]
[New LWP 18799]
[New LWP 18800]
[New LWP 18801]
[New LWP 18802]
[New LWP 18803]
[New LWP 18804]
[New LWP 18805]
[New LWP 18806]
[New LWP 18807]
[New LWP 18808]
[New LWP 18809]
[New LWP 18810]
[New LWP 18811]
[New LWP 18812]
[New LWP 18813]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x00007f08a4fd648d in poll () from /usr/lib/libc.so.6
backtrace written to /tmp/darktable_bt_THJ5UY.txt
Speicherzugriffsfehler (Speicherabzug geschrieben)

You can find the bachtrace file appended.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 07 February 2017, 19:12 GMT
Reason for closing:  Fixed
Comment by Sergej Pupykin (sergej) - Friday, 03 February 2017, 16:27 GMT
can it be reproduced with 2.2.3 ?
Comment by Stephan Munsch (forest_bear59) - Friday, 03 February 2017, 19:30 GMT
I have tested version 2.2.3 with the problematic RAW files. Problem does NOT persist.

It's ok!

Thank You for the quick reaction.

Loading...