Bug 219419 - digikam crashes after splash screen with PTP
Summary: digikam crashes after splash screen with PTP
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ProgressManager-Splashscreen (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 265770 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-20 13:56 UTC by Bernhard M. Wiedemann
Modified: 2022-02-05 12:59 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard M. Wiedemann 2009-12-20 13:56:38 UTC
Application that crashed: digikam
Version of the application: 0.10.0
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-default i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
I attached my Canon PowerShot 430 (which does PTP) to my openSUSE-11.2 KDE-install and it pops up a notifier that I can run DigiKam on it. Doing so shows the splash screen for 1-2 seconds and then segfaults (signal 11).
This happens even with empty SD-card in it.
I only used DigiKam first time today with a Sony-ericson mobile phone (which acts as mass-storage) and it at least showed images there.

Other Info:
digikam-0.10.0-7.6.i586
# rpm -qa|grep -i exiv
libexiv2-5-0.18.2-2.1.i586      
libkexiv2-7-4.3.1-3.3.i586  

# rpm -qa|grep -i xine
phonon-backend-xine-4.3.1-3.3.i586
libxine1-pulse-1.1.16.1-7.6.i586
xinetd-2.3.14-143.2.i586
libxine1-1.1.16.1-7.6.i586
phonon-backend-xine-debuginfo-4.3.1-3.3.i586
libxine1-gnome-vfs-1.1.16.1-7.6.i586
libxine1-debuginfo-1.1.16.1-7.6.i586

maybe unrelated: also crashes now without PTP, but not right after splash-screen

 -- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0xb308b700 (LWP 16262))]

Thread 5 (Thread 0xb1a13b70 (LWP 16264)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4de9d95 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122
#2  0xb4edb27c in __pthread_cond_wait (cond=0x847a430, mutex=0x847a418) at forward.c:139
#3  0xb50e7750 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0x0829a1c8 in Digikam::ScanController::run (this=0x846fc08) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:412
#6  0xb50e6623 in QThreadPrivate::start (arg=0x846fc08) at thread/qthread_unix.cpp:188
#7  0xb4de56e5 in start_thread (arg=0x0) at pthread_create.c:297
#8  0xb4de5600 in ?? () at pthread_create.c:216 from /lib/libpthread.so.0

Thread 4 (Thread 0xb0ec9b70 (LWP 16266)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4de9d95 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122
#2  0xb4edb27c in __pthread_cond_wait (cond=0x84b3ba8, mutex=0x84b3b90) at forward.c:139
#3  0xb50e7750 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0xb6ab82cc in Digikam::LoadSaveThread::run (this=0x85129d0) at /usr/src/debug/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:131
#6  0xb50e6623 in QThreadPrivate::start (arg=0x85129d0) at thread/qthread_unix.cpp:188
#7  0xb4de56e5 in start_thread (arg=0x0) at pthread_create.c:297
#8  0xb4de5600 in ?? () at pthread_create.c:216 from /lib/libpthread.so.0

Thread 3 (Thread 0xb0639b70 (LWP 16267)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4de9d95 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122
#2  0xb4edb27c in __pthread_cond_wait (cond=0x8494c98, mutex=0x8494c80) at forward.c:139
#3  0xb50e7750 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0xb6ab82cc in Digikam::LoadSaveThread::run (this=0x847f598) at /usr/src/debug/digikam-0.10.0/libs/threadimageio/loadsavethread.cpp:131
#6  0xb50e6623 in QThreadPrivate::start (arg=0x847f598) at thread/qthread_unix.cpp:188
#7  0xb4de56e5 in start_thread (arg=0x0) at pthread_create.c:297
#8  0xb4de5600 in ?? () at pthread_create.c:216 from /lib/libpthread.so.0

Thread 2 (Thread 0xae5c4b70 (LWP 16268)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4dea0c2 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:179
#2  0xb4edb2d4 in __pthread_cond_timedwait (cond=0x85e2e78, mutex=0x85e2e60, abstime=0xae5c4330) at forward.c:152
#3  0xae6c00ab in metronom_sync_loop (this=0x85e2e18) at metronom.c:870
#4  0xb4de56e5 in start_thread (arg=0x0) at pthread_create.c:297
#5  0xb4de5600 in ?? () at pthread_create.c:216 from /lib/libpthread.so.0

Thread 1 (Thread 0xb308b700 (LWP 16262)):
[KCrash Handler]
#6  xshm_open_plugin (class_gen=0x85e63f8, visual_gen=0x8587bd0) at video_out_xcbshm.c:1161
#7  0xae6c8ec8 in _load_video_driver (data=<value optimized out>, node=<value optimized out>, this=<value optimized out>) at load_plugins.c:1563
#8  _x_load_video_output_plugin (data=<value optimized out>, node=<value optimized out>, this=<value optimized out>) at load_plugins.c:1605
#9  0xae6c8f60 in xine_open_video_driver (this=0x85a4838, id=0xae73df38 "auto", visual_type=11, visual=0x8587bd0) at load_plugins.c:1627
#10 0xae73c092 in Phonon::Xine::VideoWidgetXT::createVideoPort (this=0x8587bc0) at /usr/src/debug/phonon-4.3.1/xine/videowidget.cpp:185
#11 0xae73d14d in Phonon::Xine::VideoWidget::VideoWidget (this=0x85e40b0, parent=0x8488e00) at /usr/src/debug/phonon-4.3.1/xine/videowidget.cpp:221
#12 0xae72be51 in Phonon::Xine::Backend::createObject (this=0x85a3b98, c=VideoWidgetClass, parent=0x8488e00, args=...) at /usr/src/debug/phonon-4.3.1/xine/backend.cpp:175
#13 0xb7810624 in Phonon::Factory::createVideoWidget (parent=0x8488e00) at /usr/src/debug/phonon-4.3.1/phonon/factory.cpp:326
#14 0xb7814607 in Phonon::VideoWidgetPrivate::createBackendObject (this=0x858fe70) at /usr/src/debug/phonon-4.3.1/phonon/videowidget.cpp:75
#15 0xb78142eb in Phonon::VideoWidget::VideoWidget (this=0x8488e00, parent=0x857ec00) at /usr/src/debug/phonon-4.3.1/phonon/videowidget.cpp:47
#16 0xb78155cb in Phonon::VideoPlayerPrivate::init (this=0x851b3b0, q=0x857ec00, category=VideoCategory) at /usr/src/debug/phonon-4.3.1/phonon/videoplayer.cpp:61
#17 0xb78158b5 in Phonon::VideoPlayer::VideoPlayer (this=0x857ec00, category=VideoCategory, parent=0x854c380) at /usr/src/debug/phonon-4.3.1/phonon/videoplayer.cpp:75
#18 0x0828cf95 in Digikam::MediaPlayerView::MediaPlayerView (this=0x857cda8, parent=0x85a4838) at /usr/src/debug/digikam-0.10.0/digikam/mediaplayerview.cpp:108
#19 0x0823bdb8 in Digikam::AlbumWidgetStack::AlbumWidgetStack (this=0x8493ba0, parent=0x8460220) at /usr/src/debug/digikam-0.10.0/digikam/albumwidgetstack.cpp:121
#20 0x08269378 in Digikam::DigikamView::DigikamView (this=0x847efe8, parent=0x8482038) at /usr/src/debug/digikam-0.10.0/digikam/digikamview.cpp:198
#21 0x0824d6b2 in Digikam::DigikamApp::setupView (this=0x8482038) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:427
#22 0x0825bb9c in Digikam::DigikamApp::DigikamApp (this=0x8482038, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/digikam-0.10.0/digikam/digikamapp.cpp:195
#23 0x082c1c18 in main (argc=3, argv=0xbfe01204) at /usr/src/debug/digikam-0.10.0/digikam/main.cpp:167

Reported using DrKonqi
Comment 1 caulier.gilles 2009-12-20 14:15:40 UTC
It's clear. crash appear in KDE Phonon component, when Xine loading driver is performed...

Gilles Caulier
Comment 2 Bernhard M. Wiedemann 2009-12-20 16:04:06 UTC
digikam stopped segfaulting after KDE logout+login
Comment 3 Dario Andres 2009-12-20 17:16:51 UTC
May be it was some problem while configuring the screen properties or something.
If it can't be reproduced then I will close as WORKSFORME. Thanks
Comment 4 Dario Andres 2010-03-14 13:40:06 UTC
*** Bug 227773 has been marked as a duplicate of this bug. ***
Comment 5 Pino Toscano 2011-02-08 10:23:34 UTC
*** Bug 265770 has been marked as a duplicate of this bug. ***
Comment 6 caulier.gilles 2018-08-21 13:56:56 UTC
This problem is not reproducible since digiKam use QtAv framework + ffmpeg to handle video files