digiKam › digikam-users

Crash (Lumix DMC-FZ30)

classic Classic list List threaded Threaded
♦
♦
 5 messages Options
Benjamí Villoslada
Reply | Threaded
Open this post in threaded view
♦
♦
|

Crash (Lumix DMC-FZ30)

Benjamí Villoslada
Hi,

I'm digiKam user in Debian Sid with 2 cameras:

- Canon Ixus 50
- Lumix / Panasonic DMC-FZ30

The Canon camera works fine but, not the Lumix.  Problem: crashes when read
camera photos.  digiKam detects one DMC-FZ20.  I've tried DMC-FZ30 and "USB
PTP Class Camera" with the same result: crashes.

Messages when I launch digiKam from the console:

------------------------------------------------------------
$ digikam
KIPI (loading): KIPI::PluginLoader: plugin KameraKlient is in the ignore list
for host application
KIPI (loading): Plugin_JPEGLossless plugin loaded
[...]
KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter
KCrash: Application 'digikam' crashing...
QSocketNotifier: invalid socket 15 and type 'Read', disabling...
QSocketNotifier: invalid socket 13 and type 'Read', disabling...
QSocketNotifier: invalid socket 9 and type 'Read', disabling...
QSocketNotifier: invalid socket 4 and type 'Read', disabling...
QSocketNotifier: invalid socket 14 and type 'Read', disabling...
QSocketNotifier: invalid socket 7 and type 'Read', disabling...
QSocketNotifier: invalid socket 12 and type 'Read', disabling...
digikam: Fatal IO error: client killed
------------------------------------------------------------

I copy&paste the error from KDE crash window below [1]

Versions:
digikam 0.8.1-4
igikamimageplugins 0.8.1-1
kipi-plugins 0.1+rc1-3
libkipi0 0.1.2-3

$ uname -a
Linux itaca 2.6.16-1-686-smp #1 SMP Mon Apr 3 13:02:49 UTC 2006 i686 GNU/Linux

Note: in SUSE 9.1 I can use this camera without problems (as USB PTP Class
Camera).  SUSE versions:

digikamimageplugins-0.7.4-8
digikam-0.7.4-9
kipi-plugins-0.1.0rc1-5
libkipi-0.1.1-3

------------------------------------------------------------
[1]
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1507146048 (LWP 12346)]
[New Thread -1516541008 (LWP 12448)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xa63a4399 in ioctl () from /lib/tls/i686/cmov/libc.so.6
#2  0xa664aae0 in XUnlockDisplay () from /usr/X11R6/lib/libX11.so.6
#3  0xa664ae08 in _X11TransBytesReadable () from /usr/X11R6/lib/libX11.so.6
#4  0xa662f998 in _XEventsQueued () from /usr/X11R6/lib/libX11.so.6
#5  0xa661fcc3 in XPending () from /usr/X11R6/lib/libX11.so.6
#6  0xa6aa32e2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#7  0xa6b17255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#8  0xa6b1717a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#9  0xa6afd38d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#10 0x0804a508 in main ()
------------------------------------------------------------

Thanks!


--
Benjamí
http://blog.bitassa.cat



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

Re: Crash (Lumix DMC-FZ30)

Gilles Caulier-2
Hi Ben,

One important information is missing : witch Gphoto2 version you use ?

All camera are direved by Gphoto2 not digiKam itself.

Also, your backtrace cannot be used. You need to run digiKam into gdb and give
us the backtrace when crash appear using 'bt' gdb command.

regards

Gilles Caulier

Le Samedi 8 Avril 2006 04:57, Benjamí Villoslada a écrit :

> Hi,
>
> I'm digiKam user in Debian Sid with 2 cameras:
>
> - Canon Ixus 50
> - Lumix / Panasonic DMC-FZ30
>
> The Canon camera works fine but, not the Lumix.  Problem: crashes when read
> camera photos.  digiKam detects one DMC-FZ20.  I've tried DMC-FZ30 and "USB
> PTP Class Camera" with the same result: crashes.
>
> Messages when I launch digiKam from the console:
>
> ------------------------------------------------------------
> $ digikam
> KIPI (loading): KIPI::PluginLoader: plugin KameraKlient is in the ignore
> list for host application
> KIPI (loading): Plugin_JPEGLossless plugin loaded
> [...]
> KIPI (loading): KIPI::PluginLoader: Loaded plugin RawConverter
> KCrash: Application 'digikam' crashing...
> QSocketNotifier: invalid socket 15 and type 'Read', disabling...
> QSocketNotifier: invalid socket 13 and type 'Read', disabling...
> QSocketNotifier: invalid socket 9 and type 'Read', disabling...
> QSocketNotifier: invalid socket 4 and type 'Read', disabling...
> QSocketNotifier: invalid socket 14 and type 'Read', disabling...
> QSocketNotifier: invalid socket 7 and type 'Read', disabling...
> QSocketNotifier: invalid socket 12 and type 'Read', disabling...
> digikam: Fatal IO error: client killed
> ------------------------------------------------------------
>
> I copy&paste the error from KDE crash window below [1]
>
> Versions:
> digikam 0.8.1-4
> igikamimageplugins 0.8.1-1
> kipi-plugins 0.1+rc1-3
> libkipi0 0.1.2-3
>
> $ uname -a
> Linux itaca 2.6.16-1-686-smp #1 SMP Mon Apr 3 13:02:49 UTC 2006 i686
> GNU/Linux
>
> Note: in SUSE 9.1 I can use this camera without problems (as USB PTP Class
> Camera).  SUSE versions:
>
> digikamimageplugins-0.7.4-8
> digikam-0.7.4-9
> kipi-plugins-0.1.0rc1-5
> libkipi-0.1.1-3
>
> ------------------------------------------------------------
> [1]
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread -1507146048 (LWP 12346)]
> [New Thread -1516541008 (LWP 12448)]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> 0xffffe410 in __kernel_vsyscall ()
> #0  0xffffe410 in __kernel_vsyscall ()
> #1  0xa63a4399 in ioctl () from /lib/tls/i686/cmov/libc.so.6
> #2  0xa664aae0 in XUnlockDisplay () from /usr/X11R6/lib/libX11.so.6
> #3  0xa664ae08 in _X11TransBytesReadable () from /usr/X11R6/lib/libX11.so.6
> #4  0xa662f998 in _XEventsQueued () from /usr/X11R6/lib/libX11.so.6
> #5  0xa661fcc3 in XPending () from /usr/X11R6/lib/libX11.so.6
> #6  0xa6aa32e2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
> #7  0xa6b17255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
> #8  0xa6b1717a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
> #9  0xa6afd38d in QApplication::exec () from /usr/lib/libqt-mt.so.3
> #10 0x0804a508 in main ()
> ------------------------------------------------------------
>
> Thanks!
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Benjamí Villoslada
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: Crash (Lumix DMC-FZ30)

Benjamí Villoslada
A Dissabte 08 Abril 2006 11:06, Gilles Caulier va escriure:
> One important information is missing : witch Gphoto2 version you use ?

Yes! I'm sorry:

gphoto2: 2.1.6-3 client
libgphoto2-2: 2.1.6-8
libgphoto2-port0: 2.1.6-8

> Also, your backtrace cannot be used. You need to run digiKam into gdb and
> give us the backtrace when crash appear using 'bt' gdb command.

Here my first gdb :)

-----------------------
[...]

[Thread -1517560912 (LWP 24431) exited]
[New Thread -1517560912 (LWP 24432)]
[Thread -1517560912 (LWP 24432) exited]
[New Thread -1517560912 (LWP 24433)]
[Thread -1517560912 (LWP 24433) exited]
[New Thread -1517560912 (LWP 24434)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1517560912 (LWP 24434)]
0xa3d1b5c8 in camera_init () from /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so
-----------------------

Now I can see the messatge after crashing: «Listing files
in /store_00010001...»

--
Benjamí
http://blog.bitassa.cat



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

Re: Crash (Lumix DMC-FZ30)

Gilles Caulier-2
Le Dimanche 09 Avril 2006 04:56 AM, Benjamí Villoslada a écrit :

> A Dissabte 08 Abril 2006 11:06, Gilles Caulier va escriure:
> > One important information is missing : witch Gphoto2 version you use ?
>
> Yes! I'm sorry:
>
> gphoto2: 2.1.6-3 client
> libgphoto2-2: 2.1.6-8
> libgphoto2-port0: 2.1.6-8
>
> > Also, your backtrace cannot be used. You need to run digiKam into gdb and
> > give us the backtrace when crash appear using 'bt' gdb command.
>
> Here my first gdb :)
>
> -----------------------
> [...]
>
> [Thread -1517560912 (LWP 24431) exited]
> [New Thread -1517560912 (LWP 24432)]
> [Thread -1517560912 (LWP 24432) exited]
> [New Thread -1517560912 (LWP 24433)]
> [Thread -1517560912 (LWP 24433) exited]
> [New Thread -1517560912 (LWP 24434)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1517560912 (LWP 24434)]
> 0xa3d1b5c8 in camera_init () from /usr/lib/gphoto2/2.1.6/libgphoto2_ptp2.so
> -----------------------
>
> Now I can see the messatge after crashing: «Listing files
> in /store_00010001...»

Sounds like a crash indeep gphoto2, not digiKam With a PTP camera. Please try
to update gphoto2 package.

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

Re: Crash (Lumix DMC-FZ30)

Benjamí Villoslada
A Diumenge 09 Abril 2006 09:41, Caulier Gilles va escriure:
> Sounds like a crash indeep gphoto2, not digiKam With a PTP camera. Please
> try to update gphoto2 package.

Seems that is the last version (Debian Sid).  I go to the gphoto2 mailing
list. Thanks for your orientations!

--
Benjamí
http://blog.bitassa.cat



.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Free forum by Nabble Edit this page