[digikam] [Bug 350927] New: DigiKam crash on startup

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

[digikam] [Bug 350927] New: DigiKam crash on startup

Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

            Bug ID: 350927
           Summary: DigiKam crash on startup
           Product: digikam
           Version: 4.6.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

Application: digikam (4.6.0)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-21-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
starting DigiKam saw the scan of directories and then got a crash indication
showing a segmentation fault.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2d32397880 (LWP 9311))]

Thread 5 (Thread 0x7f2d112e7700 (LWP 9312)):
#0  0x00007f2d2adfdffd in recvmsg () at /lib64/libc.so.6
#1  0x00007f2d32403fb9 in udev_monitor_receive_device () at
/usr/lib64/libudev.so.1
#2  0x00007f2d11d672eb in  () at /usr/lib64/libusb-1.0.so.0
#3  0x00007f2d28d200a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f2d2adfd08d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f2d06d1f700 (LWP 9313)):
#0  0x00007f2d28d2405f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x00007f2d2b8e1c86 in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x1567b00) at
thread/qwaitcondition_unix.cpp:86
#2  0x00007f2d2b8e1c86 in QWaitCondition::wait(QMutex*, unsigned long)
(this=<optimized out>, mutex=0x1567a08, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x00000000005e42ee in  ()
#4  0x00007f2d2b8e179f in QThreadPrivate::start(void*) (arg=0x1567780) at
thread/qthread_unix.cpp:349
#5  0x00007f2d28d200a4 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f2d2adfd08d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f2d0651e700 (LWP 9314)):
#0  0x00007f2d2adf0d2d in read () at /lib64/libc.so.6
#1  0x00007f2d1eff1f45 in  () at /usr/lib64/tls/libnvidia-tls.so.340.76
#2  0x00007f2d22e1c750 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f2d22ddb714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x00007f2d22ddbb7b in  () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f2d22ddbcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x00007f2d2ba100de in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=0x7f2cf80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#7  0x00007f2d2b9e1e6f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
(this=this@entry=0x7f2d0651dd20, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f2d2b9e2165 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)
(this=this@entry=0x7f2d0651dd20, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007f2d2b8df0bf in QThread::exec() (this=this@entry=0x14c1bc0) at
thread/qthread.cpp:538
#10 0x00007f2d2b9c3783 in QInotifyFileSystemWatcherEngine::run()
(this=0x14c1bc0) at io/qfilesystemwatcher_inotify.cpp:265
#11 0x00007f2d2b8e179f in QThreadPrivate::start(void*) (arg=0x14c1bc0) at
thread/qthread_unix.cpp:349
#12 0x00007f2d28d200a4 in start_thread () at /lib64/libpthread.so.0
#13 0x00007f2d2adfd08d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f2d05d1d700 (LWP 9317)):
#0  0x00007f2d28d2405f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x00007f2d2b8e1c86 in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x1803310) at
thread/qwaitcondition_unix.cpp:86
#2  0x00007f2d2b8e1c86 in QWaitCondition::wait(QMutex*, unsigned long)
(this=<optimized out>, mutex=0x26fc648, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x00007f2d301273fa in  () at /usr/lib64/libdigikamcore.so.4.6.0
#4  0x00007f2d2b8e179f in QThreadPrivate::start(void*) (arg=0x26fc630) at
thread/qthread_unix.cpp:349
#5  0x00007f2d28d200a4 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f2d2adfd08d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f2d32397880 (LWP 9311)):
[KCrash Handler]
#5  0x00007f2d2ada7e02 in __strcmp_sse2_unaligned () at /lib64/libc.so.6
#6  0x00007f2cf11e5fee in QMetaType::registerNormalizedType(QByteArray const&,
void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void
const*), int, QFlags<QMetaType::TypeFlag>, QMetaObject const*) () at
/usr/lib64/libQt5Core.so.5
#7  0x00007f2cf16e9f57 in  () at /usr/lib64/libQt5Gui.so.5
#8  0x00007f2d3224e92a in call_init.part () at /lib64/ld-linux-x86-64.so.2
#9  0x00007f2d3224ea13 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#10 0x00007f2d32252b48 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#11 0x00007f2d3224e7e4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#12 0x00007f2d3225233b in _dl_open () at /lib64/ld-linux-x86-64.so.2
#13 0x00007f2d217e102b in dlopen_doit () at /lib64/libdl.so.2
#14 0x00007f2d3224e7e4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#15 0x00007f2d217e15dd in _dlerror_run () at /lib64/libdl.so.2
#16 0x00007f2d217e10c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#17 0x00007f2cf787c59f in  () at /usr/lib64/libvlccore.so.7
#18 0x00007f2cf7865d5d in  () at /usr/lib64/libvlccore.so.7
#19 0x00007f2cf7866057 in  () at /usr/lib64/libvlccore.so.7
#20 0x00007f2cf78662c9 in  () at /usr/lib64/libvlccore.so.7
#21 0x00007f2cf7866534 in  () at /usr/lib64/libvlccore.so.7
#22 0x00007f2cf7866a87 in  () at /usr/lib64/libvlccore.so.7
#23 0x00007f2cf77fe49d in libvlc_InternalInit () at /usr/lib64/libvlccore.so.7
#24 0x00007f2cf75c8623 in libvlc_new () at /usr/lib64/libvlc.so.5
#25 0x00007f2cf7b00ec9 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#26 0x00007f2cf7ae6728 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#27 0x00007f2cf7ae71eb in qt_plugin_instance () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so
#28 0x00007f2d2b9c7641 in QPluginLoader::instance() (this=0x7ffd9e24a6f0) at
plugin/qpluginloader.cpp:204
#29 0x00007f2d04197f8b in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#30 0x00007f2d04198773 in  () at /usr/lib64/kde4/plugins/phonon_platform/kde.so
#31 0x00007f2d31b5bc76 in  () at /usr/lib64/libphonon.so.4
#32 0x00007f2d31b5c317 in Phonon::Factory::backend(bool) () at
/usr/lib64/libphonon.so.4
#33 0x00007f2d31b5c8e3 in  () at /usr/lib64/libphonon.so.4
#34 0x00007f2d31b549b9 in  () at /usr/lib64/libphonon.so.4
#35 0x00007f2d31b52896 in  () at /usr/lib64/libphonon.so.4
#36 0x00007f2d31b824b0 in  () at /usr/lib64/libphonon.so.4
#37 0x00007f2d31b826c3 in Phonon::VideoPlayer::mediaObject() const () at
/usr/lib64/libphonon.so.4
#38 0x0000000000686d10 in  ()
#39 0x0000000000679010 in  ()
#40 0x0000000000680853 in  ()
#41 0x000000000057e16a in  ()
#42 0x0000000000598b68 in  ()
#43 0x00000000004a0f2a in  ()
#44 0x00007f2d2ad39b05 in __libc_start_main () at /lib64/libc.so.6
#45 0x00000000004a3b4f in _start ()

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
|

[digikam] [Bug 350927] DigiKam crash on startup

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|---                         |UPSTREAM

--- Comment #1 from Gilles Caulier <[hidden email]> ---
digiKam 4.6.0 is Qt4 version.

the crash appears in Qt5 ! We don't use Qt5.

It's a packaging problem...

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 350927] DigiKam crash on startup

GPSanino
In reply to this post by Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

GPSanino <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from GPSanino <[hidden email]> ---
Hi Jim
I am having exactly the same problem, despite I installed DK 4.13.0. In fact I
got this qt5 issue despite if installing DK 4.10.0 / 4.11.0 or 4.13.0.   My
opensuse updated as usual some KDE packages and started my problems with
Digikam. As Gilles states this looks like a package issue. However it is more a
KDE issue than a Digikam, since I am experienced this segfault with other
applications as well.
Not sure what to do about it because I already did a fresh install of OpenSuSE
13.2 and with even default repos / updates + KDE:EXTRA, this qt5 issue shows up
at some point. When the system is doing its default updates during the
installation, there are steps with many packages being updated. No idea which
is the one messing this up.

Please share with us an update on this. Did you solved it somehow?

--
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 350927] DigiKam crash on startup

Jim Thale
In reply to this post by Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

--- Comment #3 from Jim Thale <[hidden email]> ---
Removing libvlccore is what did the trick.

No trees were harmed in the creation of this email,
however several billion electrons were seriously inconvenienced.

On 09/10/2015 08:10 PM, GPSanino wrote:

> https://bugs.kde.org/show_bug.cgi?id=350927
>
> GPSanino <[hidden email]> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |[hidden email]
>
> --- Comment #2 from GPSanino <[hidden email]> ---
> Hi Jim
> I am having exactly the same problem, despite I installed DK 4.13.0. In fact I
> got this qt5 issue despite if installing DK 4.10.0 / 4.11.0 or 4.13.0.   My
> opensuse updated as usual some KDE packages and started my problems with
> Digikam. As Gilles states this looks like a package issue. However it is more a
> KDE issue than a Digikam, since I am experienced this segfault with other
> applications as well.
> Not sure what to do about it because I already did a fresh install of OpenSuSE
> 13.2 and with even default repos / updates + KDE:EXTRA, this qt5 issue shows up
> at some point. When the system is doing its default updates during the
> installation, there are steps with many packages being updated. No idea which
> is the one messing this up.
>
> Please share with us an update on this. Did you solved it somehow?
>

--
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 350927] DigiKam crash on startup

Gian Paolo Sanino
In reply to this post by Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

--- Comment #4 from GPSanino <[hidden email]> ---
Thanks so much Jim

On 09/11/2015 11:58 AM, Jim Thale wrote:

> https://bugs.kde.org/show_bug.cgi?id=350927
>
> --- Comment #3 from Jim Thale <[hidden email]> ---
> Removing libvlccore is what did the trick.
>
> No trees were harmed in the creation of this email,
> however several billion electrons were seriously inconvenienced.
>
> On 09/10/2015 08:10 PM, GPSanino wrote:
>> https://bugs.kde.org/show_bug.cgi?id=350927
>>
>> GPSanino <[hidden email]> changed:
>>
>>            What    |Removed                     |Added
>> ----------------------------------------------------------------------------
>>                  CC|                            |[hidden email]
>>
>> --- Comment #2 from GPSanino <[hidden email]> ---
>> Hi Jim
>> I am having exactly the same problem, despite I installed DK 4.13.0. In fact I
>> got this qt5 issue despite if installing DK 4.10.0 / 4.11.0 or 4.13.0.   My
>> opensuse updated as usual some KDE packages and started my problems with
>> Digikam. As Gilles states this looks like a package issue. However it is more a
>> KDE issue than a Digikam, since I am experienced this segfault with other
>> applications as well.
>> Not sure what to do about it because I already did a fresh install of OpenSuSE
>> 13.2 and with even default repos / updates + KDE:EXTRA, this qt5 issue shows up
>> at some point. When the system is doing its default updates during the
>> installation, there are steps with many packages being updated. No idea which
>> is the one messing this up.
>>
>> Please share with us an update on this. Did you solved it somehow?
>>

--
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 350927] DigiKam crash on startup

Gian Paolo Sanino
In reply to this post by Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

--- Comment #5 from GPSanino <[hidden email]> ---
Thanks so much Jim, I did removed libvlccore8 (despite it also removed
vlc-codecs) and Digikam is not crashing again.

--
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 350927] DigiKam crash on startup

Jeff Cook
In reply to this post by Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

Jeff Cook <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #6 from Jeff Cook <[hidden email]> ---
I'd been getting this on ArchLinux. I'm using KDE 5 and have Qt 5 installed,
but Qt 4 is also installed.

This is *not* a packaging issue, it's a VLC issue. In my case, I had an
outdated git build of VLC installed, and that made Phonon feel bad. I
uninstalled vlc-git and replace with a fresh vlc from the repos (now newer than
the git build I installed way back when) and everything is working fine.

--
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 350927] DigiKam crash on startup

bugzilla_noreply
In reply to this post by Jim Thale
https://bugs.kde.org/show_bug.cgi?id=350927

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|UPSTREAM                    |FIXED
          Component|general                     |Preview
   Version Fixed In|                            |5.7.0

--- Comment #7 from [hidden email] ---
It crash in Phonon. This KDE component is used to render video. Since 5.2.0, we
switch to QtAV/ffmpeg framework. So this problem will never appear again.

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