Your message dated Mon, 13 Oct 2014 15:00:04 +0200
with message-id <[email protected]>
and subject line Fixed in 1.2
has caused the Debian Bug report #720542,
regarding geeqie: Segfault (assertion hit) if filename of unsupported file type 
specified on commandline
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
720542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720542
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: geeqie
Version: 1:1.1-8+b1
Severity: normal
Tags: upstream

Specifying a filename of an existing file that is not supported by Geeqie on
the commandline, like "geeqie foobar.txt" results in assertion hit:

ERROR:filedata.c:1101:file_data_new_group: assertion failed: (fd)
Program received signal SIGABRT, Aborted.

As far as I can tell, this issue still exists in upstream Git repo of Geeqie.
Unfortunately it is not clear to me what would be the correct way to fix it,
thus not going to attempt at providing a patch, sorry.




-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.14.4-grsec-dc (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages geeqie depends on:
ii  geeqie-common        1:1.1-8
ii  libatk1.0-0          2.12.0-1
ii  libc6                2.18-5
ii  libcairo2            1.12.16-2
ii  libexiv2-12          0.23-1
ii  libfontconfig1       2.11.0-5
ii  libfreetype6         2.5.2-1
ii  libgcc1              1:4.9.0-2
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libglib2.0-0         2.40.0-3
ii  libgtk2.0-0          2.24.23-1
ii  libjpeg8             8d-2
ii  liblcms1             1.19.dfsg1-1.3
ii  liblircclient0       0.9.0~pre1-1
ii  libpango-1.0-0       1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libpangoft2-1.0-0    1.36.3-1
ii  libstdc++6           4.9.0-2
ii  libtiff5             4.0.3-8

Versions of packages geeqie recommends:
ii  exiftran         2.07-12
ii  exiv2            0.23-1
ii  imagemagick      8:6.7.7.10+dfsg-1
ii  librsvg2-common  2.40.2-1
pn  ufraw-batch      <none>
ii  zenity           3.8.0-1

Versions of packages geeqie suggests:
ii  geeqie-dbg     1:1.1-8+b1
ii  gimp           2.8.10-1
pn  libjpeg-progs  <none>
pn  ufraw          <none>
pn  xpaint         <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: geeqie
Source-Version: 1:1.2-1

Hi

the patch in this bug has been already included in upstream 1.2 so is
part of current Debian package.

-- 
        Michal Čihař | http://cihar.com | http://blog.cihar.com

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to