Bug#585938: [Pkg-kde-extras] Bug#585938: I'm still getting a segfault

2010-06-16 Thread Mark Purcell
On Thursday 17 June 2010 03:04:02 Jason Woofenden wrote:
> If a backtrace of geeqie with libexiv2-6 0.19-3 would still be useful, 
> please let me know how I can get my hands on libexiv2-dbg that is 
> compatible with this version. I tried building libexiv2 from source 
> (apt-get source libexiv2-6, etc) but it did not produce a -dbg package.

Sorry to muck you around so much Jason.

It appears that some versions of geeqie were built against the broken version 
of exiv2/0.19-2.

geeqie/1:1.0-4 is correctly forced to ignore exiv2/0.19-2 and depends on 
exiv2/0.19-3.

So to clean up your system you should install geeqie/1:1.0-4 & exiv2/0.19-3, 
and remove exiv2/0.20 from experimental.


Mark


signature.asc
Description: This is a digitally signed message part.


Bug#585938: [Pkg-kde-extras] Bug#585938: I'm still getting a segfault

2010-06-16 Thread Mark Purcell
On Wednesday 16 June 2010 21:24:23 Andreas Huggel wrote:
> This std::list was introduced with the bugfix for the Nikon
> performance problem. It used to be std::vector before. So it looks
> like either the Debian exiv2 0.19-3 package didn't undo all of the
> changes of 0.19-2 (check the typedef for ExifMetadata in exif.hpp) or
> a 0.19-2 library was used to create this crash (which is not binary
> compatible with the original 0.19 because of exactly this type
> change).

Thanks Andreas,

It appears that some versions of geeqie were built against the broken version 
of exiv2/0.19-2.

geeqie/1:1.0-4 is correctly forced to ignore exiv2/0.19-2 and depends on 
exiv2/0.19-3.

Mark


signature.asc
Description: This is a digitally signed message part.


Bug#585938: [Pkg-kde-extras] Bug#585938: I'm still getting a segfault

2010-06-16 Thread Jason Woofenden

On 06/16/2010 05:56 AM, Mark Purcell wrote:

On Wednesday 16 June 2010 14:20:34 Jason Woofenden wrote:

Please let me know if I can help further (and how exactly).


Thks Jason,

Could you please install the libexiv2-dbg so we might get a better backtrack 
result.

Mark


OK, so libexiv2-dbg isn't in unstable, so I went to grab it from 
experimental, but found a later version (0.20) which is for libexiv2-9 
(not 2-6, which is what I had) so I grabbed all these from experimental: 
exiv2 libexiv2-9 libexiv2-dbg


and installed them. Then I went to get a new backtrace from gdb/geeqie, 
but it was still using the old version of libexiv2.


So I changed the symbolic link at /usr/lib/libexiv2.so.6 to point to the 
new libexiv2 (/usr/lib/libexiv2.so.9) and now geeqie doesn't crash.



If a backtrace of geeqie with libexiv2-6 0.19-3 would still be useful, 
please let me know how I can get my hands on libexiv2-dbg that is 
compatible with this version. I tried building libexiv2 from source 
(apt-get source libexiv2-6, etc) but it did not produce a -dbg package.


Take care,   - Jason



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#585938: I'm still getting a segfault

2010-06-16 Thread Andreas Huggel
> Program received signal SIGSEGV, Segmentation fault.
> 0xb787060f in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&) () from
> /usr/lib/libexiv2.so.6
> (gdb) bt
> #0  0xb787060f in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&) ()
> from /usr/lib/libexiv2.so.6
> #1  0x08095af2 in std::list std::allocator >::operator=(std::list std::allocator > const&) ()

This std::list was introduced with the bugfix for the Nikon
performance problem. It used to be std::vector before. So it looks
like either the Debian exiv2 0.19-3 package didn't undo all of the
changes of 0.19-2 (check the typedef for ExifMetadata in exif.hpp) or
a 0.19-2 library was used to create this crash (which is not binary
compatible with the original 0.19 because of exactly this type
change).

Andreas



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#585938: [Pkg-kde-extras] Bug#585938: I'm still getting a segfault

2010-06-16 Thread Mark Purcell
On Wednesday 16 June 2010 14:20:34 Jason Woofenden wrote:
> Please let me know if I can help further (and how exactly).

Thks Jason,

Could you please install the libexiv2-dbg so we might get a better backtrack 
result.

Mark


signature.asc
Description: This is a digitally signed message part.


Bug#585938: I'm still getting a segfault

2010-06-15 Thread Jason Woofenden

Hey all,

I'm still getting a segfault from geeqie. Here's what gdb has to say:

> gdb geeqie
GNU gdb (GDB) 7.1-debian
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/geeqie...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/geeqie
[Thread debugging using libthread_db enabled]
Could not init LIRC support

Program received signal SIGSEGV, Segmentation fault.
0xb787060f in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&) () 
from /usr/lib/libexiv2.so.6

(gdb) bt
#0  0xb787060f in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&) 
() from /usr/lib/libexiv2.so.6
#1  0x08095af2 in std::liststd::allocator 
>::operator=(std::liststd::allocator > const&) ()

#2  0x0809322d in ?? ()
#3  0x080916b7 in ?? ()
#4  0x080a48c3 in ?? ()
#5  0x080a58cb in ?? ()
#6  0x080f76e4 in ?? ()
#7  0x080f7751 in ?? ()
#8  0x080f8945 in ?? ()
#9  0x080f62bc in ?? ()
#10 0x08105335 in ?? ()
#11 0x08105487 in ?? ()
#12 0x08109257 in ?? ()
#13 0x081094d2 in ?? ()
#14 0x0810832a in ?? ()
#15 0x080ae129 in ?? ()
#16 0x080ae34e in ?? ()
#17 0x080b0792 in ?? ()
#18 0x080eb364 in ?? ()
#19 0x080e9195 in ?? ()
#20 0xb7a367d7 in ?? () from /lib/libglib-2.0.so.0
#21 0xb7a38163 in g_markup_parse_context_parse () from /lib/libglib-2.0.so.0
#22 0x080e93c8 in ?? ()
#23 0x080e94a7 in ?? ()
#24 0x080c2ebb in ?? ()
#25 0x080bcb49 in ?? ()
#26 0xb7587c76 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#27 0x0805ad61 in ?? ()


Not exactly what was reported at the top of this bug, but it looks like 
it's still exiv2 causing the problem.


Please let me know if I can help further (and how exactly).

Below is the reportbug output.

Thanks,- Jason



Package: geeqie
Version: 1:1.0-3
Severity: normal



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

Kernel: Linux 2.6.32-5-686 (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/dash

Versions of packages geeqie depends on:
ii  geeqie-common   1:1.0-3  data files for Geeqie
ii  libc6   2.11.2-1 Embedded GNU C Library: 
Shared lib
ii  libexiv2-6  0.19-3   EXIF/IPTC metadata 
manipulation li

ii  libgcc1 1:4.4.4-5GCC support library
ii  libglib2.0-02.24.1-1 The GLib library of C routines
ii  libgtk2.0-0 2.20.1-1 The GTK+ graphical user 
interface

ii  liblcms11.18.dfsg-1.2+b1 Color management library
ii  liblircclient0  0.8.3-5  infra-red remote control 
support -
ii  libpango1.0-0   1.28.1-1 Layout and rendering of 
internatio

ii  libstdc++6  4.4.4-5  The GNU Standard C++ Library v3

Versions of packages geeqie recommends:
ii  exiftran 2.07-3  transform digital camera 
jpeg imag
ii  exiv20.19-3  EXIF/IPTC metadata 
manipulation to

ii  imagemagick  7:6.6.0.4-2 image manipulation programs
ii  librsvg2-common  2.26.3-1SAX-based renderer library 
for SVG
ii  ufraw-batch  0.16-3  batch importer for raw 
camera imag
ii  zenity   2.30.0-1Display graphical dialog 
boxes fro


Versions of packages geeqie suggests:
pn  geeqie-dbg (no description available)
ii  gimp  2.6.8-3The GNU Image Manipulation 
Program

pn  libjpeg-progs  (no description available)
ii  ufraw 0.16-3 standalone importer for raw 
camera

pn  xpaint (no description available)

-- no debconf information



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org