libimlib2: fails to load image plugins during runtime without .la files from -dev pkg

Bug #10832 reported by Debian Bug Importer
10
Affects Status Importance Assigned to Milestone
imlib2 (Debian)
Fix Released
Unknown
imlib2 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Automatically imported from Debian bug report #283339 http://bugs.debian.org/283339

Revision history for this message
In , Achim Bohnet (allee) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Sunday 28 November 2004 11:07, Johannes Raspe wrote:
> Package: digikam
> Version: 0.7-1
> Severity: important
>
>
> Hi,
>
> when I doubleclick on a photo in digikam it should start the digikam viewer
> with this picture. Problem is that the viewer window is empty (just the
> background color). Started from console digikam gives this error when trying
> to open a picture in the viewer:
>
> digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]\
> Failed to load image: error number: 4

Hi Johannes,

I got a similar report earlier. Strange digikam 0.7-1 depends on kde 3.2.3
and not 3.3.1. The bug reporter wrote me that rebuilding
the package fixed the problem for him. Can you try too? If you don't know
how to do it check digikam deb in http://www.mpe.mpg.de/~ach/result-sid/.
I have currently only access sarge system so I can't test the rebuild deb.

Thx,
Achim
>
> With right-mouse and choosing kuickshow for displaing the picture everything
> works fine.
> This happens with lots of different jpegs (from different cameras and scanned
> ones) as well as with one .png-file I have on my disk.
>
> Regards Johannes
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (990, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.9-mm1-20041115
> Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
>
> Versions of packages digikam depends on:
> ii kdelibs4 4:3.3.1-1 KDE core libraries
> ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
> ii libgcc1 1:3.4.3-1 GCC support library
> ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime
> ii libgphoto2-2 2.1.4-8 The gphoto2 digital camera library
> ii libgphoto2-port0 2.1.4-8 The gphoto2 digital camera port li
> ii libimlib2 1.1.0-12.4 powerful image loading and renderi
> ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
> ii libkexif0 0.1-2 KDE library to read/edit EXIF info
> ii libkipi0 0.1-2 library for apps that want to use
> ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v
> ii libstdc++5 1:3.3.5-2 The GNU Standard C++ Library v3
> ii libtiff4 3.6.1-3 Tag Image File Format library
> ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li
> ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
>
> -- no debconf information
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Mark Purcell (msp) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 29 Nov 2004 11:15 am, Achim Bohnet wrote:
> > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]\
> > Failed to load image: error number: 4
> I got a similar report earlier. Strange digikam 0.7-1 depends on kde 3.2.3
> and not 3.3.1. The bug reporter wrote me that rebuilding
> the package fixed the problem for him.

I built digikam on a sarge system, hence the dependancy on kde 3.2.3.

If you like I can rebuild and upload to sarge built against kde 3.3.3.

They are supposed to be compatible, however this wound't be the first time.

Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqpdcoCzanz0IthIRAm3/AJoCCACLfA3N/keRGQaHBTOeUo1VOgCfRsOE
ps8seI2KqELqEZa/L2+JO4Q=
=xIf+
-----END PGP SIGNATURE-----

Revision history for this message
In , Paul Telford (pxt) wrote :

On Nov 28, 2004, at 7:28 PM, Mark Purcell wrote:

> I built digikam on a sarge system, hence the dependancy on kde 3.2.3.
>
> If you like I can rebuild and upload to sarge built against kde 3.3.3.

Note that KDE 3.3 won't be in Sarge when it's released, so you should
not build any version of digikam which depends on it if you plan to
upload to Sarge (or t-p-u which is the only practical way to make
changes to Sarge's digikam now). I wouldn't recommend trying to get
digikam 0.7 into Sarge at this point in any case -- please contact me
so that we can discuss it if that is truly what you meant.

I guess you really meant sid not sarge, in which case you definitely
should build against 3.3 as that is the latest version in unstable.
You should setup a sid chroot for building if you don't already have
one.

Thanks,

--
Paul Telford | 1024D/431B38BA | <email address hidden> | <email address hidden>
        C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA

Revision history for this message
In , Mark Purcell (msp) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 29 Nov 2004 03:20 pm, Paul Telford wrote:
> Note that KDE 3.3 won't be in Sarge when it's released, so you should
> not build any version of digikam which depends on it if you plan to
> upload to Sarge (or t-p-u which is the only practical way to make
> changes to Sarge's digikam now). I wouldn't recommend trying to get
> digikam 0.7 into Sarge at this point in any case -- please contact me
> so that we can discuss it if that is truly what you meant.

No it wasn't my intention that we upload to t-p-u. I tend to build the
majority of my deb's against the testing a testing box so ensure binary
compatabilty with the testing distribution as generally dependant libraries
are usually backwards compatable, otherwise they should upgrade the soname
library.

This way they are uploaded to unstable, but can also be dropped into a testing
box.

> I guess you really meant sid not sarge, in which case you definitely
> should build against 3.3 as that is the latest version in unstable.
> You should setup a sid chroot for building if you don't already have
> one.

I have a sid box here as well, so I suppose I'll prepare a new build.

Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqr7WoCzanz0IthIRAqbQAJ4luG9wtaPAkAZtfeNbZwmUyubcpwCdELJS
0fXcK5I9hZksJoVvOtSel30=
=UVLI
-----END PGP SIGNATURE-----

Revision history for this message
In , Mark Purcell (msp) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tags 283339 pending
thanks

On Sun, 28 Nov 2004 09:07 pm, Johannes Raspe wrote:
> Package: digikam
> Version: 0.7-1
> Severity: important
>
> when I doubleclick on a photo in digikam it should start the digikam viewer
> with this picture. Problem is that the viewer window is empty (just the
> background color). Started from console digikam gives this error when
> trying to open a picture in the viewer:

Hi Johannes,

I can confirm that your bug is reproducible here when you try run
digikam-0.7-1 on a sid box. The current binaries do run fine on a sarge box,
thus I suspect there are some undocumented incompatibilities in the KDE libs
between versions.

I shall upload digikam-0.7-2 shortly which should resolve this issue for you
and allow digikam ro work correctly on a sid box.

Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqsIRoCzanz0IthIRAtBPAKCUUfl4dZ+ak2wVDsfWDUTyheuYFACgi30p
2FGUmtp/ZHDWtn2O7F8I4pc=
=8u1x
-----END PGP SIGNATURE-----

Revision history for this message
In , Holger Danielsson (holger-danielsson-t-online) wrote : digikam and bug 283339

Hi Mark,

i have read your mails concerning the bug 283339 coming with digikam
0.7-1 in sid.

>I can confirm that your bug is reproducible here when you try run
>digikam-0.7-1 on a sid box. The current binaries do run fine on a
>sarge box, thus I suspect there are some undocumented
>incompatibilities in the KDE libs between versions.

Perhaps this is a problem with libimlib2, not KDE libs. Someone wrote
in the mailing list of digikam that there are no problems with older
version of libimlib2.

Perhaps this helps!

ciao holger

Revision history for this message
In , Johannes Raspe (j-raspe) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

Hi Achim, hi Marc,

I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and still no
go!
After this I did a "debuild" on the source of the 0.7-1 code and now it works.

Johannes

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
In , Achim Bohnet (allee) wrote :

On Monday 29 November 2004 17:57, Johannes Raspe wrote:
> Hi Achim, hi Marc,
>
> I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and still no
> go!
> After this I did a "debuild" on the source of the 0.7-1 code and now it works.

Strange. Is you sid system up to date?

0.7-2 has the following deb line:

$ dpkg --info digikam_0.7-2_i386.deb | grep ^\ Depends
 Depends: kdelibs4 (>= 4:3.3.1), libc6 (>= 2.3.2.ds1-4), libgcc1 (>= 1:3.4.1-3), libgdbm3, libgphoto2-2 (>= 2.1.4-8), libgphoto2-port0 (>= 2.1.4-8), libimlib2, libjpeg62, libkexif0 (>= 0.1), libkipi0 (>= 0.1), libqt3c102-mt (>= 3:3.3.3), libstdc++5 (>= 1:3.3.4-1), libtiff4, libx11-6 | xlibs (>> 4.1.0)

Is there a difference to your home build digikam deb?

Achim
>
> Johannes
>
> --
> Johannes Raspe - <email address hidden>
> GnuPG-Key ID: D342E105
> Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Johannes Raspe (j-raspe) wrote :

Am Montag, 29. November 2004 18:34 schrieb Achim Bohnet:
> On Monday 29 November 2004 17:57, Johannes Raspe wrote:
> > Hi Achim, hi Marc,
> >
> > I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and
> > still no go!
> > After this I did a "debuild" on the source of the 0.7-1 code and now it
> > works.
>
> Strange. Is you sid system up to date?
>
> 0.7-2 has the following deb line:
>
> $ dpkg --info digikam_0.7-2_i386.deb | grep ^\ Depends
> Depends: kdelibs4 (>= 4:3.3.1), libc6 (>= 2.3.2.ds1-4), libgcc1 (>=
> 1:3.4.1-3), libgdbm3, libgphoto2-2 (>= 2.1.4-8), libgphoto2-port0 (>=
> 2.1.4-8), libimlib2, libjpeg62, libkexif0 (>= 0.1), libkipi0 (>= 0.1),
> libqt3c102-mt (>= 3:3.3.3), libstdc++5 (>= 1:3.3.4-1), libtiff4, libx11-6 |
> xlibs (>> 4.1.0)
>
> Is there a difference to your home build digikam deb?

This is my output:

dpkg --info digikam_0.7-1_i386.deb | grep ^\ Depends
 Depends: kdelibs4 (>= 4:3.3.1), libc6 (>= 2.3.2.ds1-4), libgcc1 (>=
1:3.4.1-3), libgdbm3, libgphoto2-2 (>= 2.1.4-8), libgphoto2-port0 (>=
2.1.4-8), libimlib2,libjpeg62, libkexif0 (>= 0.1), libkipi0 (>= 0.1),
libqt3c102-mt (>= 3:3.3.3), libstdc++5 (>= 1:3.3.4-1), libtiff4, libx11-6 |
xlibs (>> 4.1.0)

Same as yours.

Johannes

>
> Achim
>
> > Johannes
> >
> > --
> > Johannes Raspe - <email address hidden>
> > GnuPG-Key ID: D342E105
> > Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
In , Paul Telford (pxt) wrote :

On Mon, 29 Nov 2004, Johannes Raspe wrote:

> Hi Achim, hi Marc,
>
> I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and still no
> go!
> After this I did a "debuild" on the source of the 0.7-1 code and now it works.

FWIW, that deb works properly on my freshly updated sid system. Have you
tried "apt-get upgrade"?

 Paul.

--
Paul Telford | 1024D/431B38BA | <email address hidden> | <email address hidden>
       C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA

Revision history for this message
In , Sam Hartman (hartmans) wrote : Bug#283339: fixed in openssh-krb5 3.8.1p1-7

Source: openssh-krb5
Source-Version: 3.8.1p1-7

We believe that the bug you reported is fixed in the latest version of
openssh-krb5, which is due to be installed in the Debian FTP archive:

openssh-krb5_3.8.1p1-7.diff.gz
  to pool/main/o/openssh-krb5/openssh-krb5_3.8.1p1-7.diff.gz
openssh-krb5_3.8.1p1-7.dsc
  to pool/main/o/openssh-krb5/openssh-krb5_3.8.1p1-7.dsc
ssh-krb5_3.8.1p1-7_i386.deb
  to pool/main/o/openssh-krb5/ssh-krb5_3.8.1p1-7_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sam Hartman <email address hidden> (supplier of updated openssh-krb5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 29 Nov 2004 17:35:55 -0500
Source: openssh-krb5
Binary: ssh-krb5
Architecture: source i386
Version: 3.8.1p1-7
Distribution: unstable
Urgency: low
Maintainer: Sam Hartman <email address hidden>
Changed-By: Sam Hartman <email address hidden>
Description:
 ssh-krb5 - Secure rlogin/rsh/rcp replacement (OpenSSH with Kerberos)p
Closes: 283339
Changes:
 openssh-krb5 (3.8.1p1-7) unstable; urgency=low
 .
   * Oops, compare against length, not garbage memory; bug in previous version, Closes: #283339
Files:
 dc12870c8555918664153938719ad252 681 net extra openssh-krb5_3.8.1p1-7.dsc
 fbdf2ab100054a5bd82f675d38ea6193 167045 net extra openssh-krb5_3.8.1p1-7.diff.gz
 b3f9c6cd64eca310e6d49e55fc3e3922 706568 net extra ssh-krb5_3.8.1p1-7_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBq6XI/I12czyGJg8RAm8VAKCinaLBV0ZJkxTK1Jvgg17akyV6/ACgv0RI
wsd9Efxc+GobO3ufMNX4RSA=
=G+i7
-----END PGP SIGNATURE-----

Revision history for this message
In , Paul Telford (pxt) wrote : Re: Bug#283339: marked as done (digikam: Digikam viewer doesn't display images)

reopen 283339
thanks

Hi Sam,

 You closed the wrong bug with your upload. I think you meant #283389

Thanks,

 Paul.

--
Paul Telford | 1024D/431B38BA | <email address hidden> | <email address hidden>
       C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA

Revision history for this message
In , Sean Kellogg (skellogg) wrote : digikam: Digikam viewer doesn't display images

Not sure if this bug is closed or not, but I the reported fix of uploading
0.7-2 did not resolve the problem on my sid box. When viewing an image I
still get:

digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)] Failed
to load image:error number: 4

I am fully updated against the sid mirrors. Other thoughts as to how to
resolve the problem?

--
Sean Kellogg
2nd Year - University of Washington School of Law
GPSS Senator - Student Bar Association
Editor-at-Large - National ACS Blog [http://www.acsblog.org]
c: 206.498.8207 e: skellogg@u.washington.edu

So, let go
 ...Jump in
  ...Oh well, what you waiting for?
   ...it's all right
    ...'Cause there's beauty in the breakdown

Revision history for this message
In , Achim Bohnet (allee) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> Not sure if this bug is closed or not, but I the reported fix of uploading
> 0.7-2 did not resolve the problem on my sid box. When viewing an image I
> still get:
>
> digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)] Failed
> to load image:error number: 4
>
> I am fully updated against the sid mirrors. Other thoughts as to how to
> resolve the problem?

Hmm, let's try: for the user digikam image viewer fails:

 o is digikam started in a KDE/Gnome or whatever session?
 o are any RTLD_* of LD_* environment vars set?
 o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
          list any libs outside /usr/lib /lib or /usr/X11R6/lib?
 o what's the output of
  dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F: '{print $1}' | sort | uniq`
   and output for /usr/lib/libdigikam.so

Johannes, that the difference of the dpkg -l ` dpkg -S ...
of your working home-build 0.7-1 and not working 0.7-2?

Achim
> --
> Sean Kellogg
> 2nd Year - University of Washington School of Law
> GPSS Senator - Student Bar Association
> Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> c: 206.498.8207 e: skellogg@u.washington.edu
>
> So, let go
> ...Jump in
> ...Oh well, what you waiting for?
> ...it's all right
> ...'Cause there's beauty in the breakdown
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Achim Bohnet (allee) wrote : Re: Bug#283339: digikam and bug 283339

On Monday 29 November 2004 14:00, Holger Danielsson wrote:
> Hi Mark,
>
> i have read your mails concerning the bug 283339 coming with digikam
> 0.7-1 in sid.
>
> >I can confirm that your bug is reproducible here when you try run
> >digikam-0.7-1 on a sid box. The current binaries do run fine on a
> >sarge box, thus I suspect there are some undocumented
> >incompatibilities in the KDE libs between versions.
>
> Perhaps this is a problem with libimlib2, not KDE libs. Someone wrote
> in the mailing list of digikam that there are no problems with older
> version of libimlib2.

Hi Holger,
I could not find the mail you mention. Do you have a copy or URL?

AFAICS libimlib2 in sid and sarge are identical. The only obvious
difference is KDE. On the other hand Johannes reported that
0.7-2, that is a sid rebuild of 0.7-1, does not work for him,
but a rebuild of 0.7-1 on his own sid system did work.

Achim
>
> Perhaps this helps!
>
> ciao holger
>
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Johannes Raspe (j-raspe) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

Hi,

after today's sid update (inculding digicam 0.7-2) it works fine.
Must have been some other update execpt digicam??

From my point of view the bug can be closed.

Thanks Johannes

Am Dienstag, 30. November 2004 11:29 schrieb Achim Bohnet:
> On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > Not sure if this bug is closed or not, but I the reported fix of
> > uploading 0.7-2 did not resolve the problem on my sid box. When viewing
> > an image I still get:
> >
> > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
> > Failed to load image:error number: 4
> >
> > I am fully updated against the sid mirrors. Other thoughts as to how to
> > resolve the problem?
>
> Hmm, let's try: for the user digikam image viewer fails:
>
> o is digikam started in a KDE/Gnome or whatever session?
> o are any RTLD_* of LD_* environment vars set?
> o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> list any libs outside /usr/lib /lib or /usr/X11R6/lib?
> o what's the output of
> dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F:
> '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so
>
> Johannes, that the difference of the dpkg -l ` dpkg -S ...
> of your working home-build 0.7-1 and not working 0.7-2?
>
> Achim
>
> > --
> > Sean Kellogg
> > 2nd Year - University of Washington School of Law
> > GPSS Senator - Student Bar Association
> > Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> > c: 206.498.8207 e: skellogg@u.washington.edu
> >
> > So, let go
> > ...Jump in
> > ...Oh well, what you waiting for?
> > ...it's all right
> > ...'Cause there's beauty in the breakdown

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
In , Achim Bohnet (allee) wrote :

On Tuesday 30 November 2004 17:29, Johannes Raspe wrote:
> Hi,
>
> after today's sid update (inculding digicam 0.7-2) it works fine.

Great!

> Must have been some other update execpt digicam??

Just curiuos: Did you logout/login or reboot since yesterday?
What pkgs did you install today? (check dates of
ls -ltr /usr/share/doc | tail -40)
>
> From my point of view the bug can be closed.

Sean? Holger? Farzad?

>
> Thanks Johannes

thx for the prompt information update.

Achim
>
> Am Dienstag, 30. November 2004 11:29 schrieb Achim Bohnet:
> > On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > > Not sure if this bug is closed or not, but I the reported fix of
> > > uploading 0.7-2 did not resolve the problem on my sid box. When viewing
> > > an image I still get:
> > >
> > > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
> > > Failed to load image:error number: 4
> > >
> > > I am fully updated against the sid mirrors. Other thoughts as to how to
> > > resolve the problem?
> >
> > Hmm, let's try: for the user digikam image viewer fails:
> >
> > o is digikam started in a KDE/Gnome or whatever session?
> > o are any RTLD_* of LD_* environment vars set?
> > o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> > list any libs outside /usr/lib /lib or /usr/X11R6/lib?
> > o what's the output of
> > dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F:
> > '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so
> >
> > Johannes, that the difference of the dpkg -l ` dpkg -S ...
> > of your working home-build 0.7-1 and not working 0.7-2?
> >
> > Achim
> >
> > > --
> > > Sean Kellogg
> > > 2nd Year - University of Washington School of Law
> > > GPSS Senator - Student Bar Association
> > > Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> > > c: 206.498.8207 e: skellogg@u.washington.edu
> > >
> > > So, let go
> > > ...Jump in
> > > ...Oh well, what you waiting for?
> > > ...it's all right
> > > ...'Cause there's beauty in the breakdown
>
> --
> Johannes Raspe - <email address hidden>
> GnuPG-Key ID: D342E105
> Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Sean Kellogg (skellogg) wrote :
Download full text (7.3 KiB)

Before I get to responses to the questions, I have shut down and restarted the computer with no changes. The problem still persists, so the bug isn't ready to close from my side of things :)

I still get the same error:
digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)] Failed to load image:error number: 4

On Tuesday 30 November 2004 02:29 am, you wrote:
> On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > Not sure if this bug is closed or not, but I the reported fix of
> > uploading 0.7-2 did not resolve the problem on my sid box. When viewing
> > an image I still get:
> >
> > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
> > Failed to load image:error number: 4
> >
> > I am fully updated against the sid mirrors. Other thoughts as to how to
> > resolve the problem?
>
> Hmm, let's try: for the user digikam image viewer fails:
>
> o is digikam started in a KDE/Gnome or whatever session?

Yes, KDE 3.3.1 from Debian/Sid

> o are any RTLD_* of LD_* environment vars set?

I never set environment variables... but running 'env' reveals no variables of the type RTLD_* or LD_*

> o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> list any libs outside /usr/lib /lib or /usr/X11R6/lib?

No

> o what's the output of
> dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F:
> '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so

when run on /usr/bin/digikam:

+++-=================-=================-==================================================
ii digikam 0.7-2 digital photo management application for KDE
ii kdelibs4 3.3.1-1 KDE core libraries
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphics - runtime fil
ii libaudio2 1.7-1 The Network Audio System (NAS). (shared libraries)
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries and Timezone data
ii libexif10 0.6.9-4 The EXIF library allows you to parse an EXIF file
ii libexpat1 1.95.8-1 XML parsing C library - runtime library
ii libfam0c102 2.7.0-6 client library to control the FAM daemon
ii libfontconfig1 2.2.3-4 generic font configuration library (shared library
ii libfreetype6 2.1.7-2.3 FreeType 2 font engine, shared library files
ii libgcc1 3.4.3-1 GCC support library
ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime version)
ii libgphoto2-2 2.1.4-8 The gphoto2 digital camera library
ii libgphoto2-port0 2.1.4-8 The gphoto2 digital camera port library
ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library
ii libidn11 0.5.2-3 GNU libidn library, implementation of IETF IDN spe
ii libimlib2 1.1.2-1 powerful image loading and rendering library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG runtime library
ii libkexif0 0.1-2 KDE library to read/edit EXIF informations (runtim
ii libkipi0 0.1-2 library for app...

Read more...

Revision history for this message
In , Johannes Raspe (j-raspe) wrote :

Am Dienstag, 30. November 2004 18:05 schrieb Achim Bohnet:
> On Tuesday 30 November 2004 17:29, Johannes Raspe wrote:
> > Hi,
> >
> > after today's sid update (inculding digicam 0.7-2) it works fine.
>
> Great!
>
> > Must have been some other update execpt digicam??
>
> Just curiuos: Did you logout/login or reboot since yesterday?

I logged out of KDE and back in again, but tried that yesterday after
installing the 0.7-2 version from incoming too.

> What pkgs did you install today? (check dates of
> ls -ltr /usr/share/doc | tail -40)
>
sed
imagemagick
libmagick6
libmagick++6
libkpathsea3
tetex-bin
ssh
libimlib2-dev
libimlib2
digikam
libgstreamer-plugins0.8-0
gstreamer0.8-alsa
libbluetooth1
libgsf-1
libnautilus2-2
libplot2
mozilla-firefox
nautilus-data
nautilus
perlmagick
winesetuptk
xmms-modplug

have been updated today.

Johannes

> > From my point of view the bug can be closed.
>
> Sean? Holger? Farzad?
>
> > Thanks Johannes
>
> thx for the prompt information update.
>
> Achim
>
> > Am Dienstag, 30. November 2004 11:29 schrieb Achim Bohnet:
> > > On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > > > Not sure if this bug is closed or not, but I the reported fix of
> > > > uploading 0.7-2 did not resolve the problem on my sid box. When
> > > > viewing an image I still get:
> > > >
> > > > digikam: WARNING: [bool Digikam::ImlibInterface::load(const
> > > > QString&)] Failed to load image:error number: 4
> > > >
> > > > I am fully updated against the sid mirrors. Other thoughts as to how
> > > > to resolve the problem?
> > >
> > > Hmm, let's try: for the user digikam image viewer fails:
> > >
> > > o is digikam started in a KDE/Gnome or whatever session?
> > > o are any RTLD_* of LD_* environment vars set?
> > > o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> > > list any libs outside /usr/lib /lib or /usr/X11R6/lib?
> > > o what's the output of
> > > dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk
> > > -F: '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so
> > >
> > > Johannes, that the difference of the dpkg -l ` dpkg -S ...
> > > of your working home-build 0.7-1 and not working 0.7-2?
> > >
> > > Achim
> > >
> > > > --
> > > > Sean Kellogg
> > > > 2nd Year - University of Washington School of Law
> > > > GPSS Senator - Student Bar Association
> > > > Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> > > > c: 206.498.8207 e: skellogg@u.washington.edu
> > > >
> > > > So, let go
> > > > ...Jump in
> > > > ...Oh well, what you waiting for?
> > > > ...it's all right
> > > > ...'Cause there's beauty in the breakdown
> >
> > --
> > Johannes Raspe - <email address hidden>
> > GnuPG-Key ID: D342E105
> > Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
In , Tom Jampen (jampen) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

Hi

I'm experiencing the same problems as Sean

digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
Failed to load image: error number: 4

when double-clicking an image. I'm on sid as well. On my laptop the
problem exists with version 0.7-1 and also after todays (complete sid)
update to 0.7-2.

I might add that I'm not using KDE, but WindowMaker. Thus, I might not
have all the necessary packages installed (of cause all packages digikam
depends on are installed). I've just installed the most important kde
packages to run digikcam and konqueror (just their dependencies).

A question to the "recommended" packages:
Is the recommended package "digikamimageplugins" to be uploaded soon?
"kipi-plugins"? Both are unavailable... I used to be able to view slide
shows, but not since the update to 0.7, is this just a problem on my
side? Why does 0.7-2 not recommend the available package
"digikamplugins"?

Sorry for all those questions. Just wanted to mention that the problem
still exists.

Thanks to all who help developing those apps!

Tom

Revision history for this message
In , Achim Bohnet (allee) wrote : Bug 283339: libimlib2: Digikam viewer doesn't display images

Hi,
[cc'ed libimlib2 DD]

I installed sid + desktop task + digikam and was able to reproduce
the problem: Missing libimlib2-dev pkg. So for everyone
digikam 0.7-2 image editor shows a black window and the error

 digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
 Failed to load image:error number: 4

as a workaround do:

 a) install libimlib2-dev (pulls 15 additional pkgs here)
 b) download deb, extract to to a temp dir, copy
    usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la

Johannes, Thomas? Does a) or b) fix the problem for you too?

For the curious that don't have the problem anymore:

 o move /usr/lib/imlib2_loaders/image/*.la to another dir
 o start digikam, double click a photo and enjoy the black screen ;)
 o move the .la files back, double klick image again and TATA!
   works again.

IMHO that's not digikams fault. libimlib2 uses libltdl3. AFAIU it: libltdl
uses the .la files to locate the shared libs (and additional shared libs
if given in the .la file) to load. libimlib2 tries to dynamicly load
the image plugins from /usr/lib/imlib2_loaders/image during runtime.
This means the .la files have to be included in runtime pkg not the
development pkgs.

If noone convience me otherwise I'll reassing 283339 to libimlib2
pkgs later and set severity to serious because libimlib2 is useless
and broken without libimlib2-dev install.

Sorry for the trouble. I hope everyone can enjoy digikam 0.7 now.

Achim
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Achim Bohnet (allee) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Tuesday 30 November 2004 22:51, Thomas Jampen wrote:
[...]
> A question to the "recommended" packages:
> Is the recommended package "digikamimageplugins" to be uploaded soon?
> "kipi-plugins"? Both are unavailable... I used to be able to view slide

He, he. I wondered when the first dares to ask ;)
digikamimageplugins and kipi-plugins are still in NEW queue.

  http://developer.skolelinux.no/~pere/debian-NEW.html

Until kipi-plugins enter sid you may use:

  http://people.debian.org/~msp/kipi-plugins_0.0.cvs20041110-2_i386.deb

> shows, but not since the update to 0.7, is this just a problem on my
> side? Why does 0.7-2 not recommend the available package
> "digikamplugins"?

Because they don't work with digikam 0.7 ;)

kipi-plugins is the successor of digikamplugins. In case digikam 0.7
enters sarge, digikamplugins can be completely removed from debian archive.

Name was changed because the plugin interface was rewritten to be usable
by several KDE image apps: digikam , gwenview, kimdaba and showimg

> Sorry for all those questions. Just wanted to mention that the problem
> still exists.
>
> Thanks to all who help developing those apps!

:)

Achim
>
> Tom
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Tom Jampen (jampen) wrote : Re: Bug 283339: libimlib2: Digikam viewer doesn't display images

Hi

> as a workaround do:
>
> a) install libimlib2-dev (pulls 15 additional pkgs here)
> b) download deb, extract to to a temp dir, copy
> usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la
>
> Johannes, Thomas? Does a) or b) fix the problem for you too?

I chose workaround a) and it works! In my opinion bug can be closed (or in fact reassigned as proposed), thanks!

Cheers

Tom

Revision history for this message
In , Sean Kellogg (skellogg) wrote :

On Tuesday 30 November 2004 03:31 pm, Achim Bohnet wrote:
> a) install libimlib2-dev (pulls 15 additional pkgs here)
> b) download deb, extract to to a temp dir, copy
> usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la

Workaround (a) seems good in principle, but a recent 'apt-get update' against sid renders libimlib2-dev uninstallable

The following packages have unmet dependencies:
  libimlib2-dev: Depends: libimlib2 (= 1.1.0-12.4) but 1.1.2-1 is to be installed

'dpkg -l libimlib2' reveals that I do, in fact, have 1.1.2-1 installed.
I have not yet gone down the road workaround (b), as I like to avoid installing files that are not from a deb package... too many bad experiences.

-Sean

Revision history for this message
In , Achim Bohnet (allee) wrote :

On Wednesday 01 December 2004 01:19, Sean Kellogg wrote:
> On Tuesday 30 November 2004 03:31 pm, Achim Bohnet wrote:
> > a) install libimlib2-dev (pulls 15 additional pkgs here)
> > b) download deb, extract to to a temp dir, copy
> > usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la
>
> Workaround (a) seems good in principle, but a recent 'apt-get update' against sid renders libimlib2-dev uninstallable
>
> The following packages have unmet dependencies:
> libimlib2-dev: Depends: libimlib2 (= 1.1.0-12.4) but 1.1.2-1 is to be installed

Wait a bit until your mirror updates. ftp.debian.org and ftp.de.debian.org
have the 'right' libimlib2-dev already.

> 'dpkg -l libimlib2' reveals that I do, in fact, have 1.1.2-1 installed.
> I have not yet gone down the road workaround (b), as I like to avoid installing files that are not from a deb package... too many bad experiences.

(b) is just for 56kBaud users ;)

Achim
>
> -Sean
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Sean Kellogg (skellogg) wrote :

> Wait a bit until your mirror updates.  ftp.debian.org and ftp.de.debian.org
> have the 'right' libimlib2-dev already.

Right 'o! Everything is better now and I now have all the glory that is
digikam 0.7 (so long I have waited for red eye reduction... so long...)

I see no reason to keep the bug open, but you might want to make digikam
dependent (or at least suggest) libimlib2-dev until they get things sorted
out.

Just a thought.
-Sean

Revision history for this message
In , Holger Danielsson (holger-danielsson-t-online) wrote :

Hi Achim,

> I installed sid + desktop task + digikam and was able to reproduce
> the problem: Missing libimlib2-dev pkg. So for everyone
> digikam 0.7-2 image editor shows a black window and the error
>
> digikam: WARNING: [bool Digikam::ImlibInterface::load(const
> QString&)] Failed to load image:error number: 4
>
> as a workaround do:
>
> a) install libimlib2-dev (pulls 15 additional pkgs here)
> b) download deb, extract to to a temp dir, copy
> usr/lib/imlib2_loaders/image/*.la to
> /usr/lib/imlib2_loaders/image/*.la
>

Installing libimlib2-dev solved the problem - TATA!

ciao holger

Revision history for this message
In , Achim Bohnet (allee) wrote : Bug#283339: libimlib2: Digikam viewer doesn't display images

package digikam
retitle 283339 libimlib2: fails to load image plugins during runtime without .la files from -dev pkg
submitter 283339 !
severity 283339 serious
tags 283339 + sid
reassign 283339 libimlib2
stop

Okay, now that everyone with problems confirmed that installing
libimlib2-dev fixes a runtime problem of digikam I reassing to
libimlib2.

libimlib2: Please move the /usr/lib/imlib2_loaders/*/*.la from
libimlib2-dev to libimlib2.

Thx,
Achim
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #283339 http://bugs.debian.org/283339

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sun, 28 Nov 2004 11:07:43 +0100
From: <email address hidden> (Johannes Raspe)
To: Debian Bug Tracking System <email address hidden>
Subject: digikam: Digikam viewer doesn't display images

Package: digikam
Version: 0.7-1
Severity: important

Hi,

when I doubleclick on a photo in digikam it should start the digikam viewer
with this picture. Problem is that the viewer window is empty (just the
background color). Started from console digikam gives this error when trying
to open a picture in the viewer:

digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]\
Failed to load image: error number: 4

With right-mouse and choosing kuickshow for displaing the picture everything
works fine.
This happens with lots of different jpegs (from different cameras and scanned
ones) as well as with one .png-file I have on my disk.

Regards Johannes

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-mm1-20041115
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages digikam depends on:
ii kdelibs4 4:3.3.1-1 KDE core libraries
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-1 GCC support library
ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime
ii libgphoto2-2 2.1.4-8 The gphoto2 digital camera library
ii libgphoto2-port0 2.1.4-8 The gphoto2 digital camera port li
ii libimlib2 1.1.0-12.4 powerful image loading and renderi
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libkexif0 0.1-2 KDE library to read/edit EXIF info
ii libkipi0 0.1-2 library for apps that want to use
ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v
ii libstdc++5 1:3.3.5-2 The GNU Standard C++ Library v3
ii libtiff4 3.6.1-3 Tag Image File Format library
ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li
ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m

-- no debconf information

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.1 KiB)

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 01:15:57 +0100
From: Achim Bohnet <email address hidden>
To: <email address hidden> (Johannes Raspe),
 <email address hidden>
Cc: Mark Purcell <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Sunday 28 November 2004 11:07, Johannes Raspe wrote:
> Package: digikam
> Version: 0.7-1
> Severity: important
>
>
> Hi,
>
> when I doubleclick on a photo in digikam it should start the digikam viewer
> with this picture. Problem is that the viewer window is empty (just the
> background color). Started from console digikam gives this error when trying
> to open a picture in the viewer:
>
> digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]\
> Failed to load image: error number: 4

Hi Johannes,

I got a similar report earlier. Strange digikam 0.7-1 depends on kde 3.2.3
and not 3.3.1. The bug reporter wrote me that rebuilding
the package fixed the problem for him. Can you try too? If you don't know
how to do it check digikam deb in http://www.mpe.mpg.de/~ach/result-sid/.
I have currently only access sarge system so I can't test the rebuild deb.

Thx,
Achim
>
> With right-mouse and choosing kuickshow for displaing the picture everything
> works fine.
> This happens with lots of different jpegs (from different cameras and scanned
> ones) as well as with one .png-file I have on my disk.
>
> Regards Johannes
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (990, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.9-mm1-20041115
> Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
>
> Versions of packages digikam depends on:
> ii kdelibs4 4:3.3.1-1 KDE core libraries
> ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
> ii libgcc1 1:3.4.3-1 GCC support library
> ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime
> ii libgphoto2-2 2.1.4-8 The gphoto2 digital camera library
> ii libgphoto2-port0 2.1.4-8 The gphoto2 digital camera port li
> ii libimlib2 1.1.0-12.4 powerful image loading and renderi
> ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
> ii libkexif0 0.1-2 KDE library to read/edit EXIF info
> ii libkipi0 0.1-2 library for apps that want to use
> ii libqt3c102-mt 3:3.3.3-7 Qt GUI Library (Threaded runtime v
> ii libstdc++5 1:3.3.5-2 The GNU Standard C++ Library v3
> ii libtiff4 3.6.1-3 Tag Image File Format library
> ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li
> ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
>
> -- no debconf information
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy@l...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 14:28:23 +1100
From: Mark Purcell <email address hidden>
To: Achim Bohnet <email address hidden>
Cc: <email address hidden> (Johannes Raspe),
 <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 29 Nov 2004 11:15 am, Achim Bohnet wrote:
> > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]\
> > Failed to load image: error number: 4
> I got a similar report earlier. Strange digikam 0.7-1 depends on kde 3.2=
=2E3
> and not 3.3.1. The bug reporter wrote me that rebuilding
> the package fixed the problem for him. =20

I built digikam on a sarge system, hence the dependancy on kde 3.2.3. =20

If you like I can rebuild and upload to sarge built against kde 3.3.3.

They are supposed to be compatible, however this wound't be the first time.

Mark
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqpdcoCzanz0IthIRAm3/AJoCCACLfA3N/keRGQaHBTOeUo1VOgCfRsOE
ps8seI2KqELqEZa/L2+JO4Q=3D
=3DxIf+
=2D----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sun, 28 Nov 2004 20:20:44 -0800
From: Paul Telford <email address hidden>
To: <email address hidden>,
 Mark Purcell <email address hidden>
Cc: Achim Bohnet <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Nov 28, 2004, at 7:28 PM, Mark Purcell wrote:

> I built digikam on a sarge system, hence the dependancy on kde 3.2.3.
>
> If you like I can rebuild and upload to sarge built against kde 3.3.3.

Note that KDE 3.3 won't be in Sarge when it's released, so you should
not build any version of digikam which depends on it if you plan to
upload to Sarge (or t-p-u which is the only practical way to make
changes to Sarge's digikam now). I wouldn't recommend trying to get
digikam 0.7 into Sarge at this point in any case -- please contact me
so that we can discuss it if that is truly what you meant.

I guess you really meant sid not sarge, in which case you definitely
should build against 3.3 as that is the latest version in unstable.
You should setup a sid chroot for building if you don't already have
one.

Thanks,

--
Paul Telford | 1024D/431B38BA | <email address hidden> | <email address hidden>
        C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 17:16:54 +1100
From: Mark Purcell <email address hidden>
To: Paul Telford <email address hidden>
Cc: <email address hidden>,
 Achim Bohnet <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 29 Nov 2004 03:20 pm, Paul Telford wrote:
> Note that KDE 3.3 won't be in Sarge when it's released, so you should
> not build any version of digikam which depends on it if you plan to
> upload to Sarge (or t-p-u which is the only practical way to make
> changes to Sarge's digikam now). I wouldn't recommend trying to get
> digikam 0.7 into Sarge at this point in any case -- please contact me
> so that we can discuss it if that is truly what you meant.

No it wasn't my intention that we upload to t-p-u. I tend to build the=20
majority of my deb's against the testing a testing box so ensure binary=20
compatabilty with the testing distribution as generally dependant libraries=
=20
are usually backwards compatable, otherwise they should upgrade the soname=
=20
library.

This way they are uploaded to unstable, but can also be dropped into a test=
ing=20
box.

> I guess you really meant sid not sarge, in which case you definitely
> should build against 3.3 as that is the latest version in unstable.
> You should setup a sid chroot for building if you don't already have
> one.

I have a sid box here as well, so I suppose I'll prepare a new build.

Mark
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqr7WoCzanz0IthIRAqbQAJ4luG9wtaPAkAZtfeNbZwmUyubcpwCdELJS
0fXcK5I9hZksJoVvOtSel30=3D
=3DUVLI
=2D----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 17:30:41 +1100
From: Mark Purcell <email address hidden>
To: <email address hidden> (Johannes Raspe),
 <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tags 283339 pending
thanks

On Sun, 28 Nov 2004 09:07 pm, Johannes Raspe wrote:
> Package: digikam
> Version: 0.7-1
> Severity: important
>
> when I doubleclick on a photo in digikam it should start the digikam view=
er
> with this picture. Problem is that the viewer window is empty (just the
> background color). Started from console digikam gives this error when
> trying to open a picture in the viewer:

Hi Johannes,

I can confirm that your bug is reproducible here when you try run=20
digikam-0.7-1 on a sid box. The current binaries do run fine on a sarge box=
,=20
thus I suspect there are some undocumented incompatibilities in the KDE lib=
s=20
between versions.

I shall upload digikam-0.7-2 shortly which should resolve this issue for yo=
u=20
and allow digikam ro work correctly on a sid box.

Mark
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqsIRoCzanz0IthIRAtBPAKCUUfl4dZ+ak2wVDsfWDUTyheuYFACgi30p
2FGUmtp/ZHDWtn2O7F8I4pc=3D
=3D8u1x
=2D----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 17:57:23 +0100
From: <email address hidden> (Johannes Raspe)
To: Achim Bohnet <email address hidden>,
 Mark Purcell <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

Hi Achim, hi Marc,

I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and still no
go!
After this I did a "debuild" on the source of the 0.7-1 code and now it works.

Johannes

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 18:34:53 +0100
From: Achim Bohnet <email address hidden>
To: <email address hidden> (Johannes Raspe),
 <email address hidden>
Cc: Mark Purcell <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Monday 29 November 2004 17:57, Johannes Raspe wrote:
> Hi Achim, hi Marc,
>
> I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and still no
> go!
> After this I did a "debuild" on the source of the 0.7-1 code and now it works.

Strange. Is you sid system up to date?

0.7-2 has the following deb line:

$ dpkg --info digikam_0.7-2_i386.deb | grep ^\ Depends
 Depends: kdelibs4 (>= 4:3.3.1), libc6 (>= 2.3.2.ds1-4), libgcc1 (>= 1:3.4.1-3), libgdbm3, libgphoto2-2 (>= 2.1.4-8), libgphoto2-port0 (>= 2.1.4-8), libimlib2, libjpeg62, libkexif0 (>= 0.1), libkipi0 (>= 0.1), libqt3c102-mt (>= 3:3.3.3), libstdc++5 (>= 1:3.3.4-1), libtiff4, libx11-6 | xlibs (>> 4.1.0)

Is there a difference to your home build digikam deb?

Achim
>
> Johannes
>
> --
> Johannes Raspe - <email address hidden>
> GnuPG-Key ID: D342E105
> Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 19:36:15 +0100
From: <email address hidden> (Johannes Raspe)
To: Achim Bohnet <email address hidden>
Cc: <email address hidden>,
 Mark Purcell <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

Am Montag, 29. November 2004 18:34 schrieb Achim Bohnet:
> On Monday 29 November 2004 17:57, Johannes Raspe wrote:
> > Hi Achim, hi Marc,
> >
> > I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and
> > still no go!
> > After this I did a "debuild" on the source of the 0.7-1 code and now it
> > works.
>
> Strange. Is you sid system up to date?
>
> 0.7-2 has the following deb line:
>
> $ dpkg --info digikam_0.7-2_i386.deb | grep ^\ Depends
> Depends: kdelibs4 (>= 4:3.3.1), libc6 (>= 2.3.2.ds1-4), libgcc1 (>=
> 1:3.4.1-3), libgdbm3, libgphoto2-2 (>= 2.1.4-8), libgphoto2-port0 (>=
> 2.1.4-8), libimlib2, libjpeg62, libkexif0 (>= 0.1), libkipi0 (>= 0.1),
> libqt3c102-mt (>= 3:3.3.3), libstdc++5 (>= 1:3.3.4-1), libtiff4, libx11-6 |
> xlibs (>> 4.1.0)
>
> Is there a difference to your home build digikam deb?

This is my output:

dpkg --info digikam_0.7-1_i386.deb | grep ^\ Depends
 Depends: kdelibs4 (>= 4:3.3.1), libc6 (>= 2.3.2.ds1-4), libgcc1 (>=
1:3.4.1-3), libgdbm3, libgphoto2-2 (>= 2.1.4-8), libgphoto2-port0 (>=
2.1.4-8), libimlib2,libjpeg62, libkexif0 (>= 0.1), libkipi0 (>= 0.1),
libqt3c102-mt (>= 3:3.3.3), libstdc++5 (>= 1:3.3.4-1), libtiff4, libx11-6 |
xlibs (>> 4.1.0)

Same as yours.

Johannes

>
> Achim
>
> > Johannes
> >
> > --
> > Johannes Raspe - <email address hidden>
> > GnuPG-Key ID: D342E105
> > Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 29 Nov 2004 10:59:07 -0800 (PST)
From: Paul Telford <email address hidden>
To: Johannes Raspe <email address hidden>
cc: Achim Bohnet <email address hidden>, Mark Purcell <email address hidden>,
    <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Mon, 29 Nov 2004, Johannes Raspe wrote:

> Hi Achim, hi Marc,
>
> I just tried "http://incoming.debian.org/digikam_0.7-2_i386.deb" and still no
> go!
> After this I did a "debuild" on the source of the 0.7-1 code and now it works.

FWIW, that deb works properly on my freshly updated sid system. Have you
tried "apt-get upgrade"?

 Paul.

--
Paul Telford | 1024D/431B38BA | <email address hidden> | <email address hidden>
       C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 14:00:53 +0100
From: <email address hidden> (Holger Danielsson)
To: <email address hidden>
Subject: digikam and bug 283339

Hi Mark,

i have read your mails concerning the bug 283339 coming with digikam
0.7-1 in sid.

>I can confirm that your bug is reproducible here when you try run
>digikam-0.7-1 on a sid box. The current binaries do run fine on a
>sarge box, thus I suspect there are some undocumented
>incompatibilities in the KDE libs between versions.

Perhaps this is a problem with libimlib2, not KDE libs. Someone wrote
in the mailing list of digikam that there are no problems with older
version of libimlib2.

Perhaps this helps!

ciao holger

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 18:02:05 -0500
From: Sam Hartman <email address hidden>
To: <email address hidden>
Subject: Bug#283339: fixed in openssh-krb5 3.8.1p1-7

Source: openssh-krb5
Source-Version: 3.8.1p1-7

We believe that the bug you reported is fixed in the latest version of
openssh-krb5, which is due to be installed in the Debian FTP archive:

openssh-krb5_3.8.1p1-7.diff.gz
  to pool/main/o/openssh-krb5/openssh-krb5_3.8.1p1-7.diff.gz
openssh-krb5_3.8.1p1-7.dsc
  to pool/main/o/openssh-krb5/openssh-krb5_3.8.1p1-7.dsc
ssh-krb5_3.8.1p1-7_i386.deb
  to pool/main/o/openssh-krb5/ssh-krb5_3.8.1p1-7_i386.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sam Hartman <email address hidden> (supplier of updated openssh-krb5 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 29 Nov 2004 17:35:55 -0500
Source: openssh-krb5
Binary: ssh-krb5
Architecture: source i386
Version: 3.8.1p1-7
Distribution: unstable
Urgency: low
Maintainer: Sam Hartman <email address hidden>
Changed-By: Sam Hartman <email address hidden>
Description:
 ssh-krb5 - Secure rlogin/rsh/rcp replacement (OpenSSH with Kerberos)p
Closes: 283339
Changes:
 openssh-krb5 (3.8.1p1-7) unstable; urgency=low
 .
   * Oops, compare against length, not garbage memory; bug in previous version, Closes: #283339
Files:
 dc12870c8555918664153938719ad252 681 net extra openssh-krb5_3.8.1p1-7.dsc
 fbdf2ab100054a5bd82f675d38ea6193 167045 net extra openssh-krb5_3.8.1p1-7.diff.gz
 b3f9c6cd64eca310e6d49e55fc3e3922 706568 net extra ssh-krb5_3.8.1p1-7_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBq6XI/I12czyGJg8RAm8VAKCinaLBV0ZJkxTK1Jvgg17akyV6/ACgv0RI
wsd9Efxc+GobO3ufMNX4RSA=
=G+i7
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 29 Nov 2004 15:43:54 -0800 (PST)
From: Paul Telford <email address hidden>
To: Sam Hartman <email address hidden>, <email address hidden>
Subject: Re: Bug#283339: marked as done (digikam: Digikam viewer doesn't
 display images)

reopen 283339
thanks

Hi Sam,

 You closed the wrong bug with your upload. I think you meant #283389

Thanks,

 Paul.

--
Paul Telford | 1024D/431B38BA | <email address hidden> | <email address hidden>
       C903 0E85 9AF5 1B80 6A5F F169 D7E9 4363 431B 38BA

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <200411291654.49055.skellogg@u.washington.edu>
Date: Mon, 29 Nov 2004 16:54:48 -0800
From: Sean Kellogg <skellogg@u.washington.edu>
To: <email address hidden>
Subject: digikam: Digikam viewer doesn't display images

Not sure if this bug is closed or not, but I the reported fix of uploading
0.7-2 did not resolve the problem on my sid box. When viewing an image I
still get:

digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)] Failed
to load image:error number: 4

I am fully updated against the sid mirrors. Other thoughts as to how to
resolve the problem?

--
Sean Kellogg
2nd Year - University of Washington School of Law
GPSS Senator - Student Bar Association
Editor-at-Large - National ACS Blog [http://www.acsblog.org]
c: 206.498.8207 e: skellogg@u.washington.edu

So, let go
 ...Jump in
  ...Oh well, what you waiting for?
   ...it's all right
    ...'Cause there's beauty in the breakdown

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 30 Nov 2004 11:29:01 +0100
From: Achim Bohnet <email address hidden>
To: Sean Kellogg <skellogg@u.washington.edu>,
 <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> Not sure if this bug is closed or not, but I the reported fix of uploading
> 0.7-2 did not resolve the problem on my sid box. When viewing an image I
> still get:
>
> digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)] Failed
> to load image:error number: 4
>
> I am fully updated against the sid mirrors. Other thoughts as to how to
> resolve the problem?

Hmm, let's try: for the user digikam image viewer fails:

 o is digikam started in a KDE/Gnome or whatever session?
 o are any RTLD_* of LD_* environment vars set?
 o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
          list any libs outside /usr/lib /lib or /usr/X11R6/lib?
 o what's the output of
  dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F: '{print $1}' | sort | uniq`
   and output for /usr/lib/libdigikam.so

Johannes, that the difference of the dpkg -l ` dpkg -S ...
of your working home-build 0.7-1 and not working 0.7-2?

Achim
> --
> Sean Kellogg
> 2nd Year - University of Washington School of Law
> GPSS Senator - Student Bar Association
> Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> c: 206.498.8207 e: skellogg@u.washington.edu
>
> So, let go
> ...Jump in
> ...Oh well, what you waiting for?
> ...it's all right
> ...'Cause there's beauty in the breakdown
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 30 Nov 2004 11:41:31 +0100
From: Achim Bohnet <email address hidden>
To: <email address hidden> (Holger Danielsson),
 <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#283339: digikam and bug 283339

On Monday 29 November 2004 14:00, Holger Danielsson wrote:
> Hi Mark,
>
> i have read your mails concerning the bug 283339 coming with digikam
> 0.7-1 in sid.
>
> >I can confirm that your bug is reproducible here when you try run
> >digikam-0.7-1 on a sid box. The current binaries do run fine on a
> >sarge box, thus I suspect there are some undocumented
> >incompatibilities in the KDE libs between versions.
>
> Perhaps this is a problem with libimlib2, not KDE libs. Someone wrote
> in the mailing list of digikam that there are no problems with older
> version of libimlib2.

Hi Holger,
I could not find the mail you mention. Do you have a copy or URL?

AFAICS libimlib2 in sid and sarge are identical. The only obvious
difference is KDE. On the other hand Johannes reported that
0.7-2, that is a sid rebuild of 0.7-1, does not work for him,
but a rebuild of 0.7-1 on his own sid system did work.

Achim
>
> Perhaps this helps!
>
> ciao holger
>
>
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 30 Nov 2004 17:29:15 +0100
From: <email address hidden> (Johannes Raspe)
To: Achim Bohnet <email address hidden>
Cc: Sean Kellogg <skellogg@u.washington.edu>,
 <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

Hi,

after today's sid update (inculding digicam 0.7-2) it works fine.
Must have been some other update execpt digicam??

=46rom my point of view the bug can be closed.

Thanks Johannes

Am Dienstag, 30. November 2004 11:29 schrieb Achim Bohnet:
> On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > Not sure if this bug is closed or not, but I the reported fix of
> > uploading 0.7-2 did not resolve the problem on my sid box. When viewing
> > an image I still get:
> >
> > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
> > Failed to load image:error number: 4
> >
> > I am fully updated against the sid mirrors. Other thoughts as to how to
> > resolve the problem?
>
> Hmm, let's try: for the user digikam image viewer fails:
>
> o is digikam started in a KDE/Gnome or whatever session?
> o are any RTLD_* of LD_* environment vars set?
> o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> list any libs outside /usr/lib /lib or /usr/X11R6/lib?
> o what's the output of
> dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F:
> '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so
>
> Johannes, that the difference of the dpkg -l ` dpkg -S ...
> of your working home-build 0.7-1 and not working 0.7-2?
>
> Achim
>
> > --
> > Sean Kellogg
> > 2nd Year - University of Washington School of Law
> > GPSS Senator - Student Bar Association
> > Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> > c: 206.498.8207 e: skellogg@u.washington.edu
> >
> > So, let go
> > ...Jump in
> > ...Oh well, what you waiting for?
> > ...it's all right
> > ...'Cause there's beauty in the breakdown

=2D-=20
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
=46ingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 30 Nov 2004 18:05:10 +0100
From: Achim Bohnet <email address hidden>
To: <email address hidden> (Johannes Raspe),
 <email address hidden>
Cc: Sean Kellogg <skellogg@u.washington.edu>, <email address hidden>,
 Farzad FARID <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Tuesday 30 November 2004 17:29, Johannes Raspe wrote:
> Hi,
>
> after today's sid update (inculding digicam 0.7-2) it works fine.

Great!

> Must have been some other update execpt digicam??

Just curiuos: Did you logout/login or reboot since yesterday?
What pkgs did you install today? (check dates of
ls -ltr /usr/share/doc | tail -40)
>
> From my point of view the bug can be closed.

Sean? Holger? Farzad?

>
> Thanks Johannes

thx for the prompt information update.

Achim
>
> Am Dienstag, 30. November 2004 11:29 schrieb Achim Bohnet:
> > On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > > Not sure if this bug is closed or not, but I the reported fix of
> > > uploading 0.7-2 did not resolve the problem on my sid box. When viewing
> > > an image I still get:
> > >
> > > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
> > > Failed to load image:error number: 4
> > >
> > > I am fully updated against the sid mirrors. Other thoughts as to how to
> > > resolve the problem?
> >
> > Hmm, let's try: for the user digikam image viewer fails:
> >
> > o is digikam started in a KDE/Gnome or whatever session?
> > o are any RTLD_* of LD_* environment vars set?
> > o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> > list any libs outside /usr/lib /lib or /usr/X11R6/lib?
> > o what's the output of
> > dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F:
> > '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so
> >
> > Johannes, that the difference of the dpkg -l ` dpkg -S ...
> > of your working home-build 0.7-1 and not working 0.7-2?
> >
> > Achim
> >
> > > --
> > > Sean Kellogg
> > > 2nd Year - University of Washington School of Law
> > > GPSS Senator - Student Bar Association
> > > Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> > > c: 206.498.8207 e: skellogg@u.washington.edu
> > >
> > > So, let go
> > > ...Jump in
> > > ...Oh well, what you waiting for?
> > > ...it's all right
> > > ...'Cause there's beauty in the breakdown
>
> --
> Johannes Raspe - <email address hidden>
> GnuPG-Key ID: D342E105
> Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (7.6 KiB)

Message-Id: <200411300942.44102.skellogg@u.washington.edu>
Date: Tue, 30 Nov 2004 09:42:43 -0800
From: Sean Kellogg <skellogg@u.washington.edu>
To: <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

Before I get to responses to the questions, I have shut down and restarted the computer with no changes. The problem still persists, so the bug isn't ready to close from my side of things :)

I still get the same error:
digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)] Failed to load image:error number: 4

On Tuesday 30 November 2004 02:29 am, you wrote:
> On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > Not sure if this bug is closed or not, but I the reported fix of
> > uploading 0.7-2 did not resolve the problem on my sid box. When viewing
> > an image I still get:
> >
> > digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
> > Failed to load image:error number: 4
> >
> > I am fully updated against the sid mirrors. Other thoughts as to how to
> > resolve the problem?
>
> Hmm, let's try: for the user digikam image viewer fails:
>
> o is digikam started in a KDE/Gnome or whatever session?

Yes, KDE 3.3.1 from Debian/Sid

> o are any RTLD_* of LD_* environment vars set?

I never set environment variables... but running 'env' reveals no variables of the type RTLD_* or LD_*

> o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> list any libs outside /usr/lib /lib or /usr/X11R6/lib?

No

> o what's the output of
> dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk -F:
> '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so

when run on /usr/bin/digikam:

+++-=================-=================-==================================================
ii digikam 0.7-2 digital photo management application for KDE
ii kdelibs4 3.3.1-1 KDE core libraries
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphics - runtime fil
ii libaudio2 1.7-1 The Network Audio System (NAS). (shared libraries)
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries and Timezone data
ii libexif10 0.6.9-4 The EXIF library allows you to parse an EXIF file
ii libexpat1 1.95.8-1 XML parsing C library - runtime library
ii libfam0c102 2.7.0-6 client library to control the FAM daemon
ii libfontconfig1 2.2.3-4 generic font configuration library (shared library
ii libfreetype6 2.1.7-2.3 FreeType 2 font engine, shared library files
ii libgcc1 3.4.3-1 GCC support library
ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime version)
ii libgphoto2-2 2.1.4-8 The gphoto2 digital camera library
ii libgphoto2-port0 2.1.4-8 The gphoto2 digital camera port library
ii libice6 4.3.0.dfsg.1-8 Inter-Client Exchange library
ii libidn11 0.5.2-3 GNU libidn library, implementation of IETF IDN spe
ii libimlib2 1.1.2-1 powerful image loading and rendering...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.1 KiB)

Message-Id: <email address hidden>
Date: Tue, 30 Nov 2004 20:35:17 +0100
From: <email address hidden> (Johannes Raspe)
To: Achim Bohnet <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

Am Dienstag, 30. November 2004 18:05 schrieb Achim Bohnet:
> On Tuesday 30 November 2004 17:29, Johannes Raspe wrote:
> > Hi,
> >
> > after today's sid update (inculding digicam 0.7-2) it works fine.
>
> Great!
>
> > Must have been some other update execpt digicam??
>
> Just curiuos: Did you logout/login or reboot since yesterday?

I logged out of KDE and back in again, but tried that yesterday after
installing the 0.7-2 version from incoming too.

> What pkgs did you install today? (check dates of
> ls -ltr /usr/share/doc | tail -40)
>
sed
imagemagick
libmagick6
libmagick++6
libkpathsea3
tetex-bin
ssh
libimlib2-dev
libimlib2
digikam
libgstreamer-plugins0.8-0
gstreamer0.8-alsa
libbluetooth1
libgsf-1
libnautilus2-2
libplot2
mozilla-firefox
nautilus-data
nautilus
perlmagick
winesetuptk
xmms-modplug

have been updated today.

Johannes

> > From my point of view the bug can be closed.
>
> Sean? Holger? Farzad?
>
> > Thanks Johannes
>
> thx for the prompt information update.
>
> Achim
>
> > Am Dienstag, 30. November 2004 11:29 schrieb Achim Bohnet:
> > > On Tuesday 30 November 2004 01:54, Sean Kellogg wrote:
> > > > Not sure if this bug is closed or not, but I the reported fix of
> > > > uploading 0.7-2 did not resolve the problem on my sid box. When
> > > > viewing an image I still get:
> > > >
> > > > digikam: WARNING: [bool Digikam::ImlibInterface::load(const
> > > > QString&)] Failed to load image:error number: 4
> > > >
> > > > I am fully updated against the sid mirrors. Other thoughts as to how
> > > > to resolve the problem?
> > >
> > > Hmm, let's try: for the user digikam image viewer fails:
> > >
> > > o is digikam started in a KDE/Gnome or whatever session?
> > > o are any RTLD_* of LD_* environment vars set?
> > > o Does 'ldd /usr/bin/digikam' or 'ldd /usr/lib/libdigikam.so'
> > > list any libs outside /usr/lib /lib or /usr/X11R6/lib?
> > > o what's the output of
> > > dpkg -l ` dpkg -S \`ldd /usr/bin/digikam | awk '{print $3}'\` | awk
> > > -F: '{print $1}' | sort | uniq` and output for /usr/lib/libdigikam.so
> > >
> > > Johannes, that the difference of the dpkg -l ` dpkg -S ...
> > > of your working home-build 0.7-1 and not working 0.7-2?
> > >
> > > Achim
> > >
> > > > --
> > > > Sean Kellogg
> > > > 2nd Year - University of Washington School of Law
> > > > GPSS Senator - Student Bar Association
> > > > Editor-at-Large - National ACS Blog [http://www.acsblog.org]
> > > > c: 206.498.8207 e: skellogg@u.washington.edu
> > > >
> > > > So, let go
> > > > ...Jump in
> > > > ...Oh well, what you waiting for?
> > > > ...it's all right
> > > > ...'Cause there's beauty in the breakdown
> >
> > --
> > Johannes Raspe - <email address hidden>
> > GnuPG-Key ID: D342E105
> > Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

--
Johannes Raspe - <email address hidden>
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 30 Nov 2004 22:51:33 +0100
From: Thomas Jampen <email address hidden>
To: <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

Hi

I'm experiencing the same problems as Sean

digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
Failed to load image: error number: 4

when double-clicking an image. I'm on sid as well. On my laptop the
problem exists with version 0.7-1 and also after todays (complete sid)
update to 0.7-2.

I might add that I'm not using KDE, but WindowMaker. Thus, I might not
have all the necessary packages installed (of cause all packages digikam
depends on are installed). I've just installed the most important kde
packages to run digikcam and konqueror (just their dependencies).

A question to the "recommended" packages:
Is the recommended package "digikamimageplugins" to be uploaded soon?
"kipi-plugins"? Both are unavailable... I used to be able to view slide
shows, but not since the update to 0.7, is this just a problem on my
side? Why does 0.7-2 not recommend the available package
"digikamplugins"?

Sorry for all those questions. Just wanted to mention that the problem
still exists.

Thanks to all who help developing those apps!

Tom

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 1 Dec 2004 00:31:14 +0100
From: Achim Bohnet <email address hidden>
To: <email address hidden>,
 Laurence J. Lane <email address hidden>
Cc: Sean Kellogg <skellogg@u.washington.edu>, <email address hidden>,
 Farzad FARID <email address hidden>, <email address hidden> (Johannes Raspe),
 Thomas Jampen <email address hidden>
Subject: Bug 283339: libimlib2: Digikam viewer doesn't display images

Hi,
[cc'ed libimlib2 DD]

I installed sid + desktop task + digikam and was able to reproduce
the problem: Missing libimlib2-dev pkg. So for everyone
digikam 0.7-2 image editor shows a black window and the error

 digikam: WARNING: [bool Digikam::ImlibInterface::load(const QString&)]
 Failed to load image:error number: 4

as a workaround do:

 a) install libimlib2-dev (pulls 15 additional pkgs here)
 b) download deb, extract to to a temp dir, copy
    usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la

Johannes, Thomas? Does a) or b) fix the problem for you too?

For the curious that don't have the problem anymore:

 o move /usr/lib/imlib2_loaders/image/*.la to another dir
 o start digikam, double click a photo and enjoy the black screen ;)
 o move the .la files back, double klick image again and TATA!
   works again.

IMHO that's not digikams fault. libimlib2 uses libltdl3. AFAIU it: libltdl
uses the .la files to locate the shared libs (and additional shared libs
if given in the .la file) to load. libimlib2 tries to dynamicly load
the image plugins from /usr/lib/imlib2_loaders/image during runtime.
This means the .la files have to be included in runtime pkg not the
development pkgs.

If noone convience me otherwise I'll reassing 283339 to libimlib2
pkgs later and set severity to serious because libimlib2 is useless
and broken without libimlib2-dev install.

Sorry for the trouble. I hope everyone can enjoy digikam 0.7 now.

Achim
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 1 Dec 2004 00:52:50 +0100
From: Achim Bohnet <email address hidden>
To: Thomas Jampen <email address hidden>,
 <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

On Tuesday 30 November 2004 22:51, Thomas Jampen wrote:
[...]
> A question to the "recommended" packages:
> Is the recommended package "digikamimageplugins" to be uploaded soon?
> "kipi-plugins"? Both are unavailable... I used to be able to view slide

He, he. I wondered when the first dares to ask ;)
digikamimageplugins and kipi-plugins are still in NEW queue.

  http://developer.skolelinux.no/~pere/debian-NEW.html

Until kipi-plugins enter sid you may use:

  http://people.debian.org/~msp/kipi-plugins_0.0.cvs20041110-2_i386.deb

> shows, but not since the update to 0.7, is this just a problem on my
> side? Why does 0.7-2 not recommend the available package
> "digikamplugins"?

Because they don't work with digikam 0.7 ;)

kipi-plugins is the successor of digikamplugins. In case digikam 0.7
enters sarge, digikamplugins can be completely removed from debian archive.

Name was changed because the plugin interface was rewritten to be usable
by several KDE image apps: digikam , gwenview, kimdaba and showimg

> Sorry for all those questions. Just wanted to mention that the problem
> still exists.
>
> Thanks to all who help developing those apps!

:)

Achim
>
> Tom
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 01 Dec 2004 01:11:55 +0100
From: Thomas Jampen <email address hidden>
To: Achim Bohnet <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug 283339: libimlib2: Digikam viewer doesn't display images

Hi

> as a workaround do:
>
> a) install libimlib2-dev (pulls 15 additional pkgs here)
> b) download deb, extract to to a temp dir, copy
> usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la
>
> Johannes, Thomas? Does a) or b) fix the problem for you too?

I chose workaround a) and it works! In my opinion bug can be closed (or in fact reassigned as proposed), thanks!

Cheers

Tom

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <200411301619.02427.skellogg@u.washington.edu>
Date: Tue, 30 Nov 2004 16:19:02 -0800
From: Sean Kellogg <skellogg@u.washington.edu>
To: Achim Bohnet <email address hidden>
Cc: <email address hidden>, "Laurence J. Lane" <email address hidden>,
 <email address hidden>, Farzad FARID <email address hidden>,
 Johannes Raspe <email address hidden>, Thomas Jampen <email address hidden>
Subject: Re: Bug 283339: libimlib2: Digikam viewer doesn't display images

On Tuesday 30 November 2004 03:31 pm, Achim Bohnet wrote:
> a) install libimlib2-dev (pulls 15 additional pkgs here)
> b) download deb, extract to to a temp dir, copy
> usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la

Workaround (a) seems good in principle, but a recent 'apt-get update' against sid renders libimlib2-dev uninstallable

The following packages have unmet dependencies:
  libimlib2-dev: Depends: libimlib2 (= 1.1.0-12.4) but 1.1.2-1 is to be installed

'dpkg -l libimlib2' reveals that I do, in fact, have 1.1.2-1 installed.
I have not yet gone down the road workaround (b), as I like to avoid installing files that are not from a deb package... too many bad experiences.

-Sean

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 1 Dec 2004 01:47:05 +0100
From: Achim Bohnet <email address hidden>
To: Sean Kellogg <skellogg@u.washington.edu>
Cc: <email address hidden>, "Laurence J. Lane" <email address hidden>, <email address hidden>,
 Farzad FARID <email address hidden>, Johannes Raspe <email address hidden>,
 Thomas Jampen <email address hidden>
Subject: Re: Bug 283339: libimlib2: Digikam viewer doesn't display images

On Wednesday 01 December 2004 01:19, Sean Kellogg wrote:
> On Tuesday 30 November 2004 03:31 pm, Achim Bohnet wrote:
> > a) install libimlib2-dev (pulls 15 additional pkgs here)
> > b) download deb, extract to to a temp dir, copy
> > usr/lib/imlib2_loaders/image/*.la to /usr/lib/imlib2_loaders/image/*.la
>
> Workaround (a) seems good in principle, but a recent 'apt-get update' against sid renders libimlib2-dev uninstallable
>
> The following packages have unmet dependencies:
> libimlib2-dev: Depends: libimlib2 (= 1.1.0-12.4) but 1.1.2-1 is to be installed

Wait a bit until your mirror updates. ftp.debian.org and ftp.de.debian.org
have the 'right' libimlib2-dev already.

> 'dpkg -l libimlib2' reveals that I do, in fact, have 1.1.2-1 installed.
> I have not yet gone down the road workaround (b), as I like to avoid installing files that are not from a deb package... too many bad experiences.

(b) is just for 56kBaud users ;)

Achim
>
> -Sean
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <200411301724.38063.skellogg@u.washington.edu>
Date: Tue, 30 Nov 2004 17:24:37 -0800
From: Sean Kellogg <skellogg@u.washington.edu>
To: Achim Bohnet <email address hidden>
Cc: <email address hidden>, "Laurence J. Lane" <email address hidden>,
 <email address hidden>, Farzad FARID <email address hidden>,
 Johannes Raspe <email address hidden>, Thomas Jampen <email address hidden>
Subject: Re: Bug 283339: libimlib2: Digikam viewer doesn't display images

> Wait a bit until your mirror updates. =A0ftp.debian.org and ftp.de.debian=
=2Eorg=20
> have the 'right' libimlib2-dev already.

Right 'o! Everything is better now and I now have all the glory that is=20
digikam 0.7 (so long I have waited for red eye reduction... so long...)

I see no reason to keep the bug open, but you might want to make digikam=20
dependent (or at least suggest) libimlib2-dev until they get things sorted=
=20
out.

Just a thought.
=2DSean

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 1 Dec 2004 06:10:26 +0100
From: <email address hidden> (Holger Danielsson)
To: Achim Bohnet <email address hidden>
Cc: <email address hidden>, "Laurence J. Lane" <email address hidden>,
 Sean Kellogg <skellogg@u.washington.edu>,
 Farzad FARID <email address hidden>, Johannes Raspe <email address hidden>,
 Thomas Jampen <email address hidden>
Subject: Re: Bug 283339: libimlib2: Digikam viewer doesn't display images

Hi Achim,

> I installed sid + desktop task + digikam and was able to reproduce
> the problem: Missing libimlib2-dev pkg. So for everyone
> digikam 0.7-2 image editor shows a black window and the error
>
> digikam: WARNING: [bool Digikam::ImlibInterface::load(const
> QString&)] Failed to load image:error number: 4
>
> as a workaround do:
>
> a) install libimlib2-dev (pulls 15 additional pkgs here)
> b) download deb, extract to to a temp dir, copy
> usr/lib/imlib2_loaders/image/*.la to
> /usr/lib/imlib2_loaders/image/*.la
>

Installing libimlib2-dev solved the problem - TATA!

ciao holger

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 1 Dec 2004 11:29:38 +0100
From: Achim Bohnet <email address hidden>
To: <email address hidden>
Cc: "Laurence J. Lane" <email address hidden>, Sean Kellogg <skellogg@u.washington.edu>,
 Farzad FARID <email address hidden>, Johannes Raspe <email address hidden>,
 Thomas Jampen <email address hidden>, <email address hidden> (Holger Danielsson)
Subject: Bug#283339: libimlib2: Digikam viewer doesn't display images

package digikam
retitle 283339 libimlib2: fails to load image plugins during runtime without .la files from -dev pkg
submitter 283339 !
severity 283339 serious
tags 283339 + sid
reassign 283339 libimlib2
stop

Okay, now that everyone with problems confirmed that installing
libimlib2-dev fixes a runtime problem of digikam I reassing to
libimlib2.

libimlib2: Please move the /usr/lib/imlib2_loaders/*/*.la from
libimlib2-dev to libimlib2.

Thx,
Achim
--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Mark Purcell (msp) wrote : Re: Bug#283339: digikam: Digikam viewer doesn't display images

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

I have uploaded digikam-0.7-3 which depends on libimlib2-dev, which provides a
temporary solution to this bug for digikam users, until libimlib2 can be
fixed.

Btw, it looks as if libimlib2 has been under a few NMU's.

Mark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBrbaWoCzanz0IthIRAkY8AJ9KcYkP7jA8J1n/ZrOr68kX22tfbgCfV9Sf
3Gg5oRYAfiso95VYUhRdWk0=
=M/oO
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 1 Dec 2004 23:18:27 +1100
From: Mark Purcell <email address hidden>
To: <email address hidden>
Cc: <email address hidden>,
 <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

All,

I have uploaded digikam-0.7-3 which depends on libimlib2-dev, which provide=
s a=20
temporary solution to this bug for digikam users, until libimlib2 can be=20
fixed.

Btw, it looks as if libimlib2 has been under a few NMU's.

Mark

=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBrbaWoCzanz0IthIRAkY8AJ9KcYkP7jA8J1n/ZrOr68kX22tfbgCfV9Sf
3Gg5oRYAfiso95VYUhRdWk0=3D
=3DM/oO
=2D----END PGP SIGNATURE-----

Revision history for this message
In , Mark Purcell (msp) wrote : Re: Bug#283792: digikam lost its plugins package during transition from 0.6.x to 0.7.x

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 2 Dec 2004 12:33 am, Ziegler Gábor wrote:
> >that a bug in libimlib2 not digikam (see #283339) as a workaround
> >you can install libimlib2-dev.
>
> There is a (new?) fresher imlib2 in the repository, it is just being
> installed, will see.

Ziegler ,

The newer version of libimlib2 (1.1.2-1) still does not fix the issue with
Digikam, you also need to install libimlib2-dev. Which will occur
automatically when/if you install digikam-0.7-3.

Please have a look at http://bugs.debian.org/283339 for all the details.

Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBrc/uoCzanz0IthIRAjW3AJ9oInEzjod5cSvXjOPvZaJGnZDInQCfUD/9
Nz/JD/LrJ2RUkWxNqMiKVxI=
=U7G+
-----END PGP SIGNATURE-----

Revision history for this message
In , Mark Purcell (msp) wrote : Re: Processed: Bug#283339: libimlib2: Digikam viewer doesn't display images

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tags 283339 - sid
thanks

I can confirm this issue effects sarge as well and should be considered
release critical for libimlib2.

That said a NMU would be trivial.

Mark

On Wed, 1 Dec 2004 09:33 pm, Debian Bug Tracking System wrote:
> Processing commands for <email address hidden>:
> > package digikam
>
> Ignoring bugs not assigned to: digikam
>
> > retitle 283339 libimlib2: fails to load image plugins during runtime
> > without .la files from -dev pkg
>
> Bug#283339: digikam: Digikam viewer doesn't display images
> Changed Bug title.
>
> > submitter 283339 !
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg Changed Bug submitter from <email address hidden>
> (Johannes Raspe) to Achim Bohnet <email address hidden>.
>
> > severity 283339 serious
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg Severity set to `serious'.
>
> > tags 283339 + sid
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg There were no tags set.
> Tags added: sid
>
> > reassign 283339 libimlib2
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg Bug reassigned from package `digikam' to
> `libimlib2'.
>
> > stop
>
> Stopping processing here.
>
> Please contact me if you need assistance.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBrdDVoCzanz0IthIRAkXkAJ9qCF1dIz0jVB+oKurJhKo7GQjy0gCePU26
e9h6jdW9scbZqJPjlei5bSk=
=yYc0
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Thu, 2 Dec 2004 01:06:38 +1100
From: Mark Purcell <email address hidden>
To: Ziegler =?iso-8859-1?q?G=E1bor?= <email address hidden>,
 <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#283792: digikam lost its plugins package during transition from 0.6.x to 0.7.x

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 2 Dec 2004 12:33 am, Ziegler G=E1bor wrote:
> >that a bug in libimlib2 not digikam (see #283339) as a workaround
> >you can install libimlib2-dev.
>
> There is a (new?) fresher imlib2 in the repository, it is just being
> installed, will see.

Ziegler ,

The newer version of libimlib2 (1.1.2-1) still does not fix the issue with=
=20
Digikam, you also need to install libimlib2-dev. Which will occur=20
automatically when/if you install digikam-0.7-3.

Please have a look at http://bugs.debian.org/283339 for all the details.

Mark
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBrc/uoCzanz0IthIRAjW3AJ9oInEzjod5cSvXjOPvZaJGnZDInQCfUD/9
Nz/JD/LrJ2RUkWxNqMiKVxI=3D
=3DU7G+
=2D----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Thu, 2 Dec 2004 01:10:29 +1100
From: Mark Purcell <email address hidden>
To: <email address hidden>
Cc: Achim Bohnet <email address hidden>, Paul Telford <email address hidden> (digikam #283339),
 <email address hidden> (Laurence J. Lane) (libimlib2 #283339)
Subject: Re: Processed: Bug#283339: libimlib2: Digikam viewer doesn't display images

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tags 283339 - sid
thanks

I can confirm this issue effects sarge as well and should be considered=20
release critical for libimlib2.

That said a NMU would be trivial.

Mark

On Wed, 1 Dec 2004 09:33 pm, Debian Bug Tracking System wrote:
> Processing commands for <email address hidden>:
> > package digikam
>
> Ignoring bugs not assigned to: digikam
>
> > retitle 283339 libimlib2: fails to load image plugins during runtime
> > without .la files from -dev pkg
>
> Bug#283339: digikam: Digikam viewer doesn't display images
> Changed Bug title.
>
> > submitter 283339 !
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg Changed Bug submitter from <email address hidden>
> (Johannes Raspe) to Achim Bohnet <email address hidden>.
>
> > severity 283339 serious
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg Severity set to `serious'.
>
> > tags 283339 + sid
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg There were no tags set.
> Tags added: sid
>
> > reassign 283339 libimlib2
>
> Bug#283339: libimlib2: fails to load image plugins during runtime without
> .la files from -dev pkg Bug reassigned from package `digikam' to
> `libimlib2'.
>
> > stop
>
> Stopping processing here.
>
> Please contact me if you need assistance.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBrdDVoCzanz0IthIRAkXkAJ9qCF1dIz0jVB+oKurJhKo7GQjy0gCePU26
e9h6jdW9scbZqJPjlei5bSk=3D
=3DyYc0
=2D----END PGP SIGNATURE-----

Revision history for this message
In , Laurence J. Lane (ljlane) wrote :

I can't claim to know much of anything about dlopen or
.la files, but tell me... what makes digikam have this
requirement that no other packages linked to libimlib2 have?

Revision history for this message
In , Laurence J. Lane (ljlane) wrote : more imlib2 vs digikam stuff

I have another question. digikam has been using libimlib2
for a long time now. Why does it suddenly have a problem
with a lack of .la files for imlib2 plugins?

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 2 Dec 2004 17:16:14 -0600
From: "Laurence J. Lane" <email address hidden>
To: <email address hidden>
Subject: libimlib2: fails to load image plugins during runtime without .la files from -dev pkg

I can't claim to know much of anything about dlopen or
.la files, but tell me... what makes digikam have this
requirement that no other packages linked to libimlib2 have?

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 2 Dec 2004 17:26:33 -0600
From: "Laurence J. Lane" <email address hidden>
To: <email address hidden>
Subject: more imlib2 vs digikam stuff

I have another question. digikam has been using libimlib2
for a long time now. Why does it suddenly have a problem
with a lack of .la files for imlib2 plugins?

Revision history for this message
In , Achim Bohnet (allee) wrote : Re: Bug#283339: more imlib2 vs digikam stuff

On Friday 03 December 2004 00:26, Laurence J. Lane wrote:

[Preface: no perfect explanation included below ;) ]
> I have another question. digikam has been using libimlib2
> for a long time now. Why does it suddenly have a problem
> with a lack of .la files for imlib2 plugins?

First digikam 0.7 is new. I never saw the problem because
I always had libimlib2-dev installed.

The new libImlib2 1.1.2 links again libltdl lib (or so, no access to
my sid system until monday) the libImlib2 1.1.0 in sarge does
not use libltdl lib.

I know that KDEs dyn loading for k-parts, services, etc since
some year relies on the existance of .la files. If this
influences the dynamic loading of libimlib. I don't kown :(

On Friday 03 December 2004 00:16, Laurence J. Lane wrote:
> I can't claim to know much of anything about dlopen or
> .la files, but tell me... what makes digikam have this
> requirement that no other packages linked to libimlib2 have?

Good question. Maybe others have libimlib2-dev also installed?

Here another 'vague' answer from Renchi the main digikam developer

----
some preface: imlib2 uses dynamically loaded file-loaders to load
different file formats (is that statement loaded enough :)). to determine
the location and type of loaders, imlib2 just needs to check the .so files
in its loader directories. but when used in conjuction with kde, the
dynamic loading of the .so files is somehow influenced (i'm not clear in
the details of this). i believe the .la files installed with the loaders
are being forced to be used (when used with kde), and if there is an
incompatibility between the location indicated by the .la files (for the
.so files) and the actual .so file location, the .so files will fail to
load. sorry for being vague, but this is all that i know. somebody with
better knowledge of dlopening and kde influence on that will be better
able to answer the question.

renchi
---

I still think the answer is the usage of libltdl (and maybe KDE).
But it's too late now to check the docs in the web.

Hope this helps at least a little bit,
Achim
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Fri, 3 Dec 2004 01:17:20 +0100
From: Achim Bohnet <email address hidden>
To: "Laurence J. Lane" <email address hidden>,
 <email address hidden>
Subject: Re: Bug#283339: more imlib2 vs digikam stuff

On Friday 03 December 2004 00:26, Laurence J. Lane wrote:

[Preface: no perfect explanation included below ;) ]
> I have another question. digikam has been using libimlib2
> for a long time now. Why does it suddenly have a problem
> with a lack of .la files for imlib2 plugins?

First digikam 0.7 is new. I never saw the problem because
I always had libimlib2-dev installed.

The new libImlib2 1.1.2 links again libltdl lib (or so, no access to
my sid system until monday) the libImlib2 1.1.0 in sarge does
not use libltdl lib.

I know that KDEs dyn loading for k-parts, services, etc since
some year relies on the existance of .la files. If this
influences the dynamic loading of libimlib. I don't kown :(

On Friday 03 December 2004 00:16, Laurence J. Lane wrote:
> I can't claim to know much of anything about dlopen or
> .la files, but tell me... what makes digikam have this
> requirement that no other packages linked to libimlib2 have?

Good question. Maybe others have libimlib2-dev also installed?

Here another 'vague' answer from Renchi the main digikam developer

----
some preface: imlib2 uses dynamically loaded file-loaders to load
different file formats (is that statement loaded enough :)). to determine
the location and type of loaders, imlib2 just needs to check the .so files
in its loader directories. but when used in conjuction with kde, the
dynamic loading of the .so files is somehow influenced (i'm not clear in
the details of this). i believe the .la files installed with the loaders
are being forced to be used (when used with kde), and if there is an
incompatibility between the location indicated by the .la files (for the
.so files) and the actual .so file location, the .so files will fail to
load. sorry for being vague, but this is all that i know. somebody with
better knowledge of dlopening and kde influence on that will be better
able to answer the question.

renchi
---

I still think the answer is the usage of libltdl (and maybe KDE).
But it's too late now to check the docs in the web.

Hope this helps at least a little bit,
Achim
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Steve Langasek (vorlon) wrote :

reassign 283339 kdelibs4
thanks

I've confirmed both that other imlib-using packages do not suffer from this
bug, and that libImlib2 uses lt_dlopenext() correctly.

This is not a bug in libimlib2; it is a bug in kdelibs4, which is statically
linking a buggy version of libltdl into /usr/lib/libkdecore.so.4.

I'm not certain that this should be considered an RC bug, since the only
affected package (digikam) has already implemented a workaround.

Thanks,
--
Steve Langasek
postmodern programmer

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Sat, 4 Dec 2004 21:38:35 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: Re: libimlib2: fails to load image plugins during runtime without .la files from -dev pkg

--BQPnanjtCNWHyqYD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassign 283339 kdelibs4
thanks

I've confirmed both that other imlib-using packages do not suffer from this
bug, and that libImlib2 uses lt_dlopenext() correctly.

This is not a bug in libimlib2; it is a bug in kdelibs4, which is statically
linking a buggy version of libltdl into /usr/lib/libkdecore.so.4.

I'm not certain that this should be considered an RC bug, since the only
affected package (digikam) has already implemented a workaround.

Thanks,
--=20
Steve Langasek
postmodern programmer

--BQPnanjtCNWHyqYD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBsp7YKN6ufymYLloRAl26AJ9ITDXM1b5a4HPCG4GsL7Gn59vZgACgzQJp
92gJ/iPDC8QdvcJhQGEqq3k=
=13GK
-----END PGP SIGNATURE-----

--BQPnanjtCNWHyqYD--

Revision history for this message
In , Riku Voipio (riku-voipio) wrote : Forward upstream, please?

severity 283339 important
tags 283339 +upstream
thanks

(Downgrading, since the only affected program is working this
 bug around)

Achim, can you forward this issue upstream? After reading this
bugreport, I don't really feel confident that I understand
the bug enough to make a sensible summary for bugs.kde.org.

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 13 Dec 2004 22:24:17 +0200
From: Riku Voipio <email address hidden>
To: <email address hidden>, Achim Bohnet <email address hidden>
Cc: <email address hidden>
Subject: Forward upstream, please?

severity 283339 important
tags 283339 +upstream
thanks

(Downgrading, since the only affected program is working this
 bug around)

Achim, can you forward this issue upstream? After reading this
bugreport, I don't really feel confident that I understand
the bug enough to make a sensible summary for bugs.kde.org.

Revision history for this message
In , Achim Bohnet (allee) wrote :

On Monday 13 December 2004 21:24, Riku Voipio wrote:

> Achim, can you forward this issue upstream? After reading this
[...]
Hi Riku,

as Renchi mentioned on digikam-devel, the bug is already reported
upstream:

 http://bugs.kde.org/show_bug.cgi?id=93359

Achim
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
In , Dato Simó (dato) wrote : Re: Bug#283339: Forward upstream, please?

forwarded 283339 http://bugs.kde.org/93359
stop here

* Achim Bohnet [Tue, 21 Dec 2004 23:03:44 +0100]:
> On Monday 13 December 2004 21:24, Riku Voipio wrote:

> > Achim, can you forward this issue upstream? After reading this
> [...]
> Hi Riku,

> as Renchi mentioned on digikam-devel, the bug is already reported
> upstream:

> http://bugs.kde.org/show_bug.cgi?id=93359

  marking as forwarded, then.

  thanks.

--
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

As scarce as truth is, the supply has always been in excess of the demand.
                -- Josh Billings

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Tue, 21 Dec 2004 23:03:44 +0100
From: Achim Bohnet <email address hidden>
To: Riku Voipio <email address hidden>
Cc: <email address hidden>
Subject: Re: Forward upstream, please?

On Monday 13 December 2004 21:24, Riku Voipio wrote:

> Achim, can you forward this issue upstream? After reading this
[...]
Hi Riku,

as Renchi mentioned on digikam-devel, the bug is already reported
upstream:

 http://bugs.kde.org/show_bug.cgi?id=93359

Achim
>
>
>

--
  To me vi is Zen. To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- <email address hidden>

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 21 Dec 2004 23:45:32 +0100
From: Adeodato =?iso-8859-1?Q?Sim=F3?= <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#283339: Forward upstream, please?

forwarded 283339 http://bugs.kde.org/93359
stop here

* Achim Bohnet [Tue, 21 Dec 2004 23:03:44 +0100]:
> On Monday 13 December 2004 21:24, Riku Voipio wrote:

> > Achim, can you forward this issue upstream? After reading this
> [...]
> Hi Riku,

> as Renchi mentioned on digikam-devel, the bug is already reported
> upstream:

> http://bugs.kde.org/show_bug.cgi?id=93359

  marking as forwarded, then.

  thanks.

--
Adeodato Sim� EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621

As scarce as truth is, the supply has always been in excess of the demand.
                -- Josh Billings

Revision history for this message
Matt Zimmerman (mdz) wrote :

Not something that we're likely to fix independently; we'll bring in the fix
from upstream/Debian when it comes

Revision history for this message
In , Debian Qt/KDE Maintainers (debian-qt-kde) wrote :

user <email address hidden>
forwarded 283339 http://bugs.kde.org/93359
usertag 283339 =
usertag 283339 + bzStatus-new
thanks

Revision history for this message
In , Pierre Habouzit (madcoder) wrote :
Download full text (26.9 KiB)

user <email address hidden>

forwarded 100894 http://bugs.kde.org/6184
usertag 6184 =
usertag 6184 + bzStatus-new
forwarded 101379 http://bugs.kde.org/32192
usertag 32192 =
usertag 32192 + bzStatus-unconfirmed
forwarded 102462 http://bugs.kde.org/35918
usertag 35918 =
usertag 35918 + bzStatus-unconfirmed
forwarded 111358 http://bugs.kde.org/35921
usertag 35921 =
usertag 35921 + bzStatus-closed
usertag 35921 + bzRes-fixed

forwarded 116824 http://bugs.kde.org/35926
usertag 35926 =
usertag 35926 + bzStatus-resolved
usertag 35926 + bzRes-wontfix

forwarded 116826 http://bugs.kde.org/22723
usertag 22723 =
usertag 22723 + bzStatus-new
forwarded 118834 http://bugs.kde.org/35938
usertag 35938 =
usertag 35938 + bzStatus-new
forwarded 131562 http://bugs.kde.org/48485
usertag 48485 =
usertag 48485 + bzStatus-resolved
usertag 48485 + bzRes-worksforme

forwarded 134368 http://bugs.kde.org/40418
usertag 40418 =
usertag 40418 + bzStatus-new
forwarded 134611 http://bugs.kde.org/54379
usertag 54379 =
usertag 54379 + bzStatus-resolved
usertag 54379 + bzRes-fixed

forwarded 135632 http://bugs.kde.org/37210
usertag 37210 =
usertag 37210 + bzStatus-new
forwarded 141094 http://bugs.kde.org/54329
usertag 54329 =
usertag 54329 + bzStatus-resolved
usertag 54329 + bzRes-fixed

forwarded 141095 http://bugs.kde.org/54330
usertag 54330 =
usertag 54330 + bzStatus-resolved
usertag 54330 + bzRes-fixed

forwarded 143457 http://bugs.kde.org/31055
usertag 31055 =
usertag 31055 + bzStatus-unconfirmed
forwarded 145786 http://bugs.kde.org/62603
usertag 62603 =
usertag 62603 + bzStatus-new
forwarded 146047 http://bugs.kde.org/54382
usertag 54382 =
usertag 54382 + bzStatus-resolved
usertag 54382 + bzRes-fixed

forwarded 147088 http://bugs.kde.org/118123
usertag 118123 =
usertag 118123 + bzStatus-unconfirmed
forwarded 158841 http://bugs.kde.org/66790
usertag 66790 =
usertag 66790 + bzStatus-resolved
usertag 66790 + bzRes-fixed

forwarded 172610 http://bugs.kde.org/59069
usertag 59069 =
usertag 59069 + bzStatus-unconfirmed
forwarded 174560 http://bugs.kde.org/67153
usertag 67153 =
usertag 67153 + bzStatus-new
forwarded 180801 http://bugs.kde.org/54845
usertag 54845 =
usertag 54845 + bzStatus-new
forwarded 180894 http://bugs.kde.org/71338
usertag 71338 =
usertag 71338 + bzStatus-reopened
forwarded 183281 http://bugs.kde.org/66020
usertag 66020 =
usertag 66020 + bzStatus-new
forwarded 185034 http://bugs.kde.org/66050
usertag 66050 =
usertag 66050 + bzStatus-new
forwarded 185116 http://bugs.kde.org/59599
usertag 59599 =
usertag 59599 + bzStatus-new
forwarded 185957 http://bugs.kde.org/70053
usertag 70053 =
usertag 70053 + bzStatus-resolved
usertag 70053 + bzRes-fixed

forwarded 186150 http://bugs.kde.org/28321
usertag 28321 =
usertag 28321 + bzStatus-new
forwarded 186164 http://bugs.kde.org/33372
usertag 33372 =
usertag 33372 + bzStatus-new
forwarded 187339 http://bugs.kde.org/43366
usertag 43366 =
usertag 43366 + bzStatus-new
forwarded 187887 http://bugs.kde.org/66049
usertag 66049 =
usertag 66049 + bzStatus-new
forwarded 190033 http://bugs.kde.org/66318
usertag 66318 =
usertag 66318 + bzStatus-resolved
usertag 66318 + bzRes-duplicate

forwarded 192045 http://bugs.kde.org/6604...

Revision history for this message
In , Pierre Habouzit (madcoder) wrote : btspull automated mail
Download full text (115.6 KiB)

user <email address hidden>
forwarded 85437 http://bugs.kde.org/show_bug.cgi?id=20186
tags 85437 + upstream fixed-upstream
usertags 85437 + status-CLOSED resolution-FIXED
tags 223708 + upstream fixed-upstream
usertags 223708 + status-CLOSED resolution-FIXED
forwarded 85443 http://bugs.kde.org/show_bug.cgi?id=20187
tags 85443 + upstream fixed-upstream
usertags 85443 + status-CLOSED resolution-FIXED
forwarded 100894 http://bugs.kde.org/show_bug.cgi?id=6184
tags 100894 + upstream
usertags 100894 + status-NEW
tags 215400 + upstream
usertags 215400 + status-NEW
tags 94567 + upstream wontfix
usertags 94567 + status-RESOLVED resolution-WONTFIX
forwarded 101379 http://bugs.kde.org/show_bug.cgi?id=32192
tags 101379 - wontfix
tags 101379 + upstream
usertags 101379 + status-UNCONFIRMED
usertags 154184 + status-RESOLVED resolution-FIXED
forwarded 102462 http://bugs.kde.org/show_bug.cgi?id=35918
usertags 102462 + status-UNCONFIRMED
forwarded 262988 http://bugzilla.kernel.org/show_bug.cgi?id=4532
tags 262988 + upstream fixed-upstream
usertags 262988 + status-CLOSED resolution-CODE_FIX
tags 132860 + upstream wontfix
usertags 132860 + status-RESOLVED resolution-WONTFIX
usertags 226824 + status-ASSIGNED
tags 221999 + upstream fixed-upstream
usertags 221999 + status-RESOLVED resolution-WORKSFORME
forwarded 103201 http://bugs.kde.org/show_bug.cgi?id=28072
tags 103201 + fixed-upstream
usertags 103201 + status-RESOLVED resolution-FIXED
usertags 169092 + status-NEW
tags 251067 + upstream
usertags 251067 + status-NEW
tags 144907 + upstream
usertags 144907 + status-ASSIGNED
forwarded 111358 http://bugs.kde.org/show_bug.cgi?id=35921
tags 111358 + upstream fixed-upstream
usertags 111358 + status-CLOSED resolution-FIXED
usertags 297529 + status-NEW
tags 223738 + upstream fixed-upstream
usertags 223738 + status-RESOLVED resolution-WORKSFORME
forwarded 116824 http://bugs.kde.org/show_bug.cgi?id=35926
usertags 116824 + status-RESOLVED resolution-WONTFIX
tags 180740 + upstream
usertags 180740 + status-REOPENED
usertags 169146 + status-NEW
tags 223928 + upstream fixed-upstream
usertags 223928 + status-RESOLVED resolution-WORKSFORME
usertags 190690 + status-UNCONFIRMED
tags 266542 + upstream
usertags 266542 + status-NEW
forwarded 116826 http://bugs.kde.org/show_bug.cgi?id=22723
usertags 116826 + status-NEW
tags 311758 + upstream
usertags 311758 + status-RESOLVED resolution-CODE_FIX
tags 303074 + upstream fixed-upstream
usertags 303074 + status-RESOLVED resolution-WORKSFORME
tags 196814 + upstream
usertags 196814 + status-NEW
tags 48602 + upstream wontfix
usertags 48602 + status-RESOLVED resolution-WONTFIX
tags 201323 + upstream
usertags 201323 + status-NEW
tags 238290 + upstream
usertags 238290 + status-NEW
forwarded 231017 https://bugzilla.icculus.org/show_bug.cgi?id=952
usertags 231017 + status-ASSIGNED
usertags 321403 + status-ASSIGNED
forwarded 118834 http://bugs.kde.org/show_bug.cgi?id=35938
usertags 118834 + status-NEW
usertags 200342 + status-NEW
tags 206744 + fixed-upstream
usertags 206744 + status-RESOLVED resolution-FIXED
tags 280412 + fixed-upstream
usertags 280412 + status-RESOLVED resolution-FIXED
tags 310141 + upstream
usertags 310141 + statu...

Revision history for this message
In , Martin Michlmayr (tbm) wrote : Please check if bugs still apply; if not, close them

reassign 283339 kdelibs4c2a

--
Martin Michlmayr
http://www.cyrius.com/

Changed in imlib2 (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.