Bug#726231: digikam crashes after start on console

[Steve M. Robbins]

Hello,

I'm sorry it's taken so long to get to your report.  But since it has been a 
while, I need to ask: does the issue still happen?

On Sun, 13 Oct 2013 18:11:49 +0200 Dirk Pankonin  wrote:

>* What was the outcome of this action?
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
> use, all queries will cease to work.
> [0x1a1db88] main services discovery error: no suitable services discovery
> module
> digikam: tiffcomposite.cpp:1037: virtual uint32_t
> Exiv2::Internal::TiffMnEntry::doCount() const: Zusicherung »tiffType() ==
> ttUndefined || tiffType() == ttUnsignedByte || tiffType() == ttSignedByte«
> nicht erfüllt.
> digikam: Fatal IO error: client killed

I can't reproduce this crash.  Have you configured digikam in any special 
manner?  Is it using the default SQLite database or is it using an external 
one such as mysql?

Thanks,
-Steve



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

Bug#726231: digikam crashes after start on console

[Dirk Pankonin]

Package: digikam
Version: 4:2.6.0-1+b2
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
Starting digikam

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Starting digikam on console

   * What was the outcome of this action?
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
[0x1a1db88] main services discovery error: no suitable services discovery
module
digikam: tiffcomposite.cpp:1037: virtual uint32_t
Exiv2::Internal::TiffMnEntry::doCount() const: Zusicherung »tiffType() ==
ttUndefined || tiffType() == ttUnsignedByte || tiffType() == ttSignedByte«
nicht erfüllt.
digikam: Fatal IO error: client killed
Unable to start Dr. Konqi

   * What outcome did you expect instead?

A digikam applicationwithout crashing.



-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages digikam depends on:
ii  digikam-data4:2.6.0-1
ii  kde-runtime 4:4.8.4-2
ii  libc6   2.13-38
ii  libgcc1 1:4.7.2-5
ii  libgomp14.7.2-5
ii  libgphoto2-22.4.14-2
ii  libgphoto2-port02.4.14-2
ii  libjasper1  1.900.1-13
ii  libjpeg88d-1
ii  libkdcraw20 4:4.8.4-1
ii  libkdecore5 4:4.8.4-4
ii  libkdeui5   4:4.8.4-4
ii  libkdewebkit5   4:4.8.4-4
ii  libkexiv2-104:4.8.4-1
ii  libkfile4   4:4.8.4-4
ii  libkhtml5   4:4.8.4-4
ii  libkio5 4:4.8.4-4
ii  libkipi84:4.8.4-1
ii  libknotifyconfig4   4:4.8.4-4
ii  libkparts4  4:4.8.4-4
ii  liblcms11.19.dfsg-1.2
ii  liblensfun0 0.2.5-2
ii  liblqr-1-0  0.4.1-2
ii  libmarblewidget13   4:4.8.4-3
ii  libnepomuk4 4:4.8.4-4
ii  libopencv-core2.3   2.3.1-11
ii  libopencv-highgui2.32.3.1-11
ii  libopencv-imgproc2.32.3.1-11
ii  libopencv-legacy2.3 2.3.1-11
ii  libopencv-objdetect2.3  2.3.1-11
ii  libphonon4  4:4.6.0.0-3
ii  libpng12-0  1.2.49-1
ii  libqjson0   0.7.1-7
ii  libqt4-dbus 4:4.8.2+dfsg-11
ii  libqt4-network  4:4.8.2+dfsg-11
ii  libqt4-qt3support   4:4.8.2+dfsg-11
ii  libqt4-sql  4:4.8.2+dfsg-11
ii  libqt4-sql-sqlite   4:4.8.2+dfsg-11
ii  libqt4-xml  4:4.8.2+dfsg-11
ii  libqtcore4  4:4.8.2+dfsg-11
ii  libqtgui4   4:4.8.2+dfsg-11
ii  libqtwebkit42.2.1-5
ii  libsolid4   4:4.8.4-4
ii  libsoprano4 2.7.6+dfsg.1-2wheezy1
ii  libstdc++6  4.7.2-5
ii  libtiff43.9.6-11
ii  libx11-62:1.5.0-1+deb7u1
ii  phonon  4:4.6.0.0-3

Versions of packages digikam recommends:
ii  chromium [www-browser]   29.0.1547.57-1~deb7u1
ii  iceweasel [www-browser]  24.0-1~bpo70+1
ii  kipi-plugins 4:2.6.0-1+b2
ii  konqueror [www-browser]  4:4.8.4-2
ii  mplayerthumbs4:4.8.4-2
ii  w3m [www-browser]0.5.3-8

Versions of packages digikam suggests:
pn  digikam-doc  none

-- no debconf information


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