[Bug 302776] New: Digikam crashes at startup

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

[Bug 302776] New: Digikam crashes at startup

Alexey Zhbanov
https://bugs.kde.org/show_bug.cgi?id=302776

            Bug ID: 302776
          Severity: crash
           Version: 2.5.0
          Priority: NOR
          Assignee: [hidden email]
           Summary: Digikam crashes at startup
    Classification: Unclassified
                OS: Linux
          Reporter: [hidden email]
          Hardware: openSUSE RPMs
            Status: UNCONFIRMED
         Component: general
           Product: digikam

Application: digikam (2.5.0)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 2.6.37.6-0.20-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
When I start Digikam, it always crashes with segmentation fault.

The crash can be reproduced every time.

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

Thread 9 (Thread 0x7f8c7a241700 (LWP 28989)):
#0  0x0000003fabe0b38c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000003fb367abbb in wait (this=<value optimized out>, mutex=0xea62e8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0xea62e8,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00000000005c0da8 in Digikam::ScanController::run (this=0xea5f60) at
/usr/src/debug/digikam-2.5.0/core/digikam/database/scancontroller.cpp:647
#4  0x0000003fb367a4d5 in QThreadPrivate::start (arg=0xea5f60) at
thread/qthread_unix.cpp:331
#5  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#6  0x0000003fab2d371d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 8 (Thread 0x7f8c79a40700 (LWP 28990)):
#0  0x0000003fabe0907a in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x0000003fade450b6 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x0000003fade45fa9 in ?? () from /lib64/libglib-2.0.so.0
#3  0x0000003fade46650 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x0000003fb378e636 in QEventDispatcherGlib::processEvents (this=0x1024330,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x0000003fb3762c22 in QEventLoop::processEvents (this=<value optimized
out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x0000003fb3762e35 in QEventLoop::exec (this=0x7f8c79a3fce0, flags=...) at
kernel/qeventloop.cpp:201
#7  0x0000003fb3677be4 in QThread::exec (this=<value optimized out>) at
thread/qthread.cpp:498
#8  0x0000003fb3744358 in QInotifyFileSystemWatcherEngine::run (this=0x1045510)
at io/qfilesystemwatcher_inotify.cpp:248
#9  0x0000003fb367a4d5 in QThreadPrivate::start (arg=0x1045510) at
thread/qthread_unix.cpp:331
#10 0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#11 0x0000003fab2d371d in clone () from /lib64/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 7 (Thread 0x7f8c7923f700 (LWP 28992)):
#0  0x0000003fabe0b38c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000003fb367abbb in wait (this=<value optimized out>, mutex=0x1152588,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1152588,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x0000003fcd337587 in Digikam::ParkingThread::run (this=0x1152570) at
/usr/src/debug/digikam-2.5.0/core/libs/threads/threadmanager.cpp:119
#4  0x0000003fb367a4d5 in QThreadPrivate::start (arg=0x1152570) at
thread/qthread_unix.cpp:331
#5  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#6  0x0000003fab2d371d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 6 (Thread 0x7f8c714de700 (LWP 28993)):
#0  0x0000003fabe0b6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000003fbe215c21 in ?? () from /usr/lib64/libxine.so.1
#2  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#3  0x0000003fab2d371d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f8c700a1700 (LWP 28994)):
#0  0x0000003fabe0b6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000003fbe223b07 in ?? () from /usr/lib64/libxine.so.1
#2  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#3  0x0000003fab2d371d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f8c6f8a0700 (LWP 28995)):
#0  0x0000003fab2ca5a3 in poll () from /lib64/libc.so.6
#1  0x0000003fade46114 in ?? () from /lib64/libglib-2.0.so.0
#2  0x0000003fade46650 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x0000003fb378e636 in QEventDispatcherGlib::processEvents (this=0x132ab40,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x0000003fb3762c22 in QEventLoop::processEvents (this=<value optimized
out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x0000003fb3762e35 in QEventLoop::exec (this=0x7f8c6f89fcd0, flags=...) at
kernel/qeventloop.cpp:201
#6  0x0000003fb3677be4 in QThread::exec (this=<value optimized out>) at
thread/qthread.cpp:498
#7  0x00007f8c76e6d694 in ?? () from
/usr/lib64/kde4/plugins/phonon_backend/phonon_xine.so
#8  0x0000003fb367a4d5 in QThreadPrivate::start (arg=0x20b7970) at
thread/qthread_unix.cpp:331
#9  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#10 0x0000003fab2d371d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f8c6ee95700 (LWP 28998)):
#0  0x0000003fab2ca5a3 in poll () from /lib64/libc.so.6
#1  0x00007f8c6ee9a977 in ?? () from
/usr/lib64/xine/plugins/1.30/xineplug_ao_out_alsa.so
#2  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#3  0x0000003fab2d371d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f8c6e694700 (LWP 28999)):
#0  0x0000003fabe0b38c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000003fbe227f8b in ?? () from /usr/lib64/libxine.so.1
#2  0x0000003fabe06a3f in start_thread () from /lib64/libpthread.so.0
#3  0x0000003fab2d371d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8c7dea5860 (LWP 28988)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x0000000000516ce9 in Digikam::KipiImageCollection::~KipiImageCollection
(this=0x2f47e90, __in_chrg=<value optimized out>) at
/usr/src/debug/digikam-2.5.0/core/utilities/kipiiface/kipiimagecollection.cpp:81
#8  0x00007f8c6777ad87 in ?? () from /usr/lib64/kde4/kipiplugin_printimages.so
#9  0x0000000000575afb in Digikam::DigikamApp::slotKipiPluginPlug
(this=0x11cc550) at
/usr/src/debug/digikam-2.5.0/core/digikam/main/digikamapp.cpp:2767
#10 0x0000000000577afd in Digikam::DigikamApp::qt_metacall (this=0x11cc550,
_c=QMetaObject::InvokeMetaMethod, _id=42, _a=0x7fff17268b10) at
/usr/src/debug/digikam-2.5.0/build/core/digikam/digikamapp.moc:259
#11 0x0000003fb3777e8f in QMetaObject::activate (sender=0x2edfa20, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x0) at
kernel/qobject.cpp:3287
#12 0x000000000056c530 in Digikam::DigikamApp::loadPlugins (this=0x11cc550) at
/usr/src/debug/digikam-2.5.0/core/digikam/main/digikamapp.cpp:2697
#13 0x000000000058283b in Digikam::DigikamApp::DigikamApp (this=0x11cc550,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at
/usr/src/debug/digikam-2.5.0/core/digikam/main/digikamapp.cpp:279
#14 0x000000000068c126 in main (argc=14878672, argv=0x7fff0000001d) at
/usr/src/debug/digikam-2.5.0/core/digikam/main/main.cpp:188

Reported using DrKonqi

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[Bug 302776] Digikam crashes at startup

Gilles Caulier-4
https://bugs.kde.org/show_bug.cgi?id=302776

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
          Component|general                     |Kipiinterface
         Resolution|---                         |WAITINGFORINFO

--- Comment #1 from Gilles Caulier <[hidden email]> ---
It crash in kipi interface. Sound like a libkipi binary compatibility broken on
your computer. Please, update to last 2.6.0 release and try again.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 302776] Digikam crashes at startup

Gilles Caulier-4
In reply to this post by Alexey Zhbanov
https://bugs.kde.org/show_bug.cgi?id=302776

--- Comment #2 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 302776] Digikam crashes at startup

Gilles Caulier-4
In reply to this post by Alexey Zhbanov
https://bugs.kde.org/show_bug.cgi?id=302776

--- Comment #3 from Gilles Caulier <[hidden email]> ---
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 302776] Digikam crashes at startup

bugzilla_noreply
In reply to this post by Alexey Zhbanov
https://bugs.kde.org/show_bug.cgi?id=302776

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |5.0.0
         Resolution|WAITINGFORINFO              |FIXED

--- Comment #4 from [hidden email] ---
With digiKam 5.0.0, this problem is not reproducible.

I close this file now. Re-open it if necessary.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 302776] Digikam crashes at startup

bugzilla_noreply
In reply to this post by Alexey Zhbanov
https://bugs.kde.org/show_bug.cgi?id=302776

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Kipiinterface               |PrintCreator

--
You are receiving this mail because:
You are the assignee for the bug.