Bug#479903: digikam: Digikam cannot be started: segmentation fault

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#479903: digikam: Digikam cannot be started: segmentation fault

Eeltje
Package: digikam
Version: 2:0.9.3-2
Severity: grave
Justification: renders package unusable


When starting digikam at first everything seems to go normally, but
after loading draw there occurs a segmentation fault and digikam
crashes:

eeltje@box:~$ digikam
Found draw version: 8.83
Segmentatiefout

It seems the problem exists since upgrading xorg to version 1:7.3+10

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

Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core)
Locale: LANG=nl_NL@euro, LC_CTYPE=nl_NL@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages digikam depends on:
ii  kdebase-kio-plugins  4:3.5.9.dfsg.1-2+b1 core I/O slaves for KDE
ii  kdelibs4c2a          4:3.5.9.dfsg.1-4    core libraries and binaries for al
ii  libc6                2.7-10              GNU C Library: Shared libraries
ii  libgcc1              1:4.3.0-3           GCC support library
ii  libgphoto2-2         2.4.0-9             gphoto2 digital camera library
ii  libgphoto2-port0     2.4.0-9             gphoto2 digital camera port librar
ii  libjasper1           1.900.1-4           The JasPer JPEG-2000 runtime libra
ii  libjpeg62            6b-14               The Independent JPEG Group's JPEG
ii  libkdcraw3           0.1.4-2             Raw picture decoding C++ library (
ii  libkexiv2-3          0.1.7-1             Qt like interface for the libexiv2
ii  libkipi0             0.1.6-1             library for apps that want to use
ii  liblcms1             1.16-10             Color management library
ii  libpng12-0           1.2.27-1            PNG library - runtime
ii  libqt3-mt            3:3.3.8b-5          Qt GUI Library (Threaded runtime v
ii  libsqlite3-0         3.5.8-1             SQLite 3 shared library
ii  libstdc++6           4.3.0-3             The GNU Standard C++ Library v3
ii  libtiff4             3.8.2-8             Tag Image File Format (TIFF) libra
ii  libx11-6             2:1.0.3-7           X11 client-side library

Versions of packages digikam recommends:
ii  kdeprint             4:3.5.9.dfsg.1-2+b1 print system for KDE
ii  kipi-plugins         0.1.5-1             image manipulation/handling plugin
ii  konqueror            4:3.5.9.dfsg.1-2+b1 KDE's advanced file manager, web b

-- no debconf information



_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Bug#479903: marked as done (digikam: Digikam cannot be started: segmentation fault)

Debian Bug Tracking System

Your message dated Wed, 21 May 2008 15:37:19 +1000 (EST)
with message-id <[hidden email]>
and subject line Possible caused by the NVidia driver
has caused the Debian Bug report #479903,
regarding digikam: Digikam cannot be started: segmentation fault
to be marked as done.

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

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


--
479903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479903
Debian Bug Tracking System
Contact [hidden email] with problems

Package: digikam
Version: 2:0.9.3-2
Severity: grave
Justification: renders package unusable


When starting digikam at first everything seems to go normally, but
after loading draw there occurs a segmentation fault and digikam
crashes:

eeltje@box:~$ digikam
Found draw version: 8.83
Segmentatiefout

It seems the problem exists since upgrading xorg to version 1:7.3+10

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

Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core)
Locale: LANG=nl_NL@euro, LC_CTYPE=nl_NL@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages digikam depends on:
ii  kdebase-kio-plugins  4:3.5.9.dfsg.1-2+b1 core I/O slaves for KDE
ii  kdelibs4c2a          4:3.5.9.dfsg.1-4    core libraries and binaries for al
ii  libc6                2.7-10              GNU C Library: Shared libraries
ii  libgcc1              1:4.3.0-3           GCC support library
ii  libgphoto2-2         2.4.0-9             gphoto2 digital camera library
ii  libgphoto2-port0     2.4.0-9             gphoto2 digital camera port librar
ii  libjasper1           1.900.1-4           The JasPer JPEG-2000 runtime libra
ii  libjpeg62            6b-14               The Independent JPEG Group's JPEG
ii  libkdcraw3           0.1.4-2             Raw picture decoding C++ library (
ii  libkexiv2-3          0.1.7-1             Qt like interface for the libexiv2
ii  libkipi0             0.1.6-1             library for apps that want to use
ii  liblcms1             1.16-10             Color management library
ii  libpng12-0           1.2.27-1            PNG library - runtime
ii  libqt3-mt            3:3.3.8b-5          Qt GUI Library (Threaded runtime v
ii  libsqlite3-0         3.5.8-1             SQLite 3 shared library
ii  libstdc++6           4.3.0-3             The GNU Standard C++ Library v3
ii  libtiff4             3.8.2-8             Tag Image File Format (TIFF) libra
ii  libx11-6             2:1.0.3-7           X11 client-side library

Versions of packages digikam recommends:
ii  kdeprint             4:3.5.9.dfsg.1-2+b1 print system for KDE
ii  kipi-plugins         0.1.5-1             image manipulation/handling plugin
ii  konqueror            4:3.5.9.dfsg.1-2+b1 KDE's advanced file manager, web b

-- no debconf information



Version: 2:0.9.3-2

Thanks Eeltje,

Btw, as the submitter of the bug you are entitled to close it directly
with an email to: [hidden email]
Mark


From: Eeltje de Vries <[hidden email]>
To: [hidden email]
Subject: Digikam
Date: Thu, 15 May 2008 11:47:13 +0200

I think the problem was caused by the NVidia driver. Now that I do net use
that driver there is no longer a problem. I think the bug can be closed!
--
Eeltje de Vries






_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel