[Bug 185638] New: digikam crash on startup

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

[Bug 185638] New: digikam crash on startup

Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638

           Summary: digikam crash on startup
           Product: digikam
           Version: 0.10.0-rc2
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:           0.10.0-rc2 (using 4.2.00 (KDE 4.2.0), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-1-686

I suspect this is similar to #185183 but doubt the issue is marble-data as
0.10.0~rc2 depends on marble-data.

http://bugs.debian.org/491458

Package: digikam
Version: 2:0.10.0~rc2-1
Followup-For: Bug #491458

herewith the dump:

Application: digiKam (digikam), signal SIGSEGV
[Current thread is 1 (Thread 0xb47c06f0 (LWP 3534))]

Thread 4 (Thread 0xb3176b90 (LWP 3537)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb50a0025 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb54977fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb567d852 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4  0x0828e879 in ?? ()
#5  0xb567c83e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb509c4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54896de in clone () from /lib/i686/cmov/libc.so.6

Thread 3 (Thread 0xb1e2db90 (LWP 3544)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb50a0025 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb54977fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb567d852 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4  0xb719cbda in Digikam::LoadSaveThread::run() () from
/usr/lib/libdigikamcore.so.1
#5  0xb567c83e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb509c4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54896de in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb262eb90 (LWP 3545)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb50a0025 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb54977fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb567d852 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4  0xb719cbda in Digikam::LoadSaveThread::run() () from
/usr/lib/libdigikamcore.so.1
#5  0xb567c83e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb509c4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54896de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb47c06f0 (LWP 3534)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb5444ef6 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb5444d0f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb68d9128 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()



-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages digikam depends on:
ii  kde-icons-oxygen       4:4.2.0-1         Oxygen icon theme for KDE 4
ii  kdebase-runtime        4:4.2.0-1         runtime components from the offici
ii  kdelibs5               4:4.2.0-3         core libraries for all KDE 4 appli
ii  kdepimlibs5            4:4.2.0-1         core libraries for KDE PIM 4 appli
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  libgcc1                1:4.3.3-4         GCC support library
ii  libgphoto2-2           2.4.1-3           gphoto2 digital camera library
ii  libgphoto2-port0       2.4.1-3           gphoto2 digital camera port librar
ii  libjasper1             1.900.1-5.1       The JasPer JPEG-2000 runtime libra
ii  libjpeg62              6b-14             The Independent JPEG Group's JPEG
ii  libkdcraw7             4:4.2.0-1         Raw picture decoding C++ library (
ii  libkexiv2-7            4:4.2.0-1         Qt like interface for the libexiv2
ii  libkipi6               4:4.2.0-1         library for apps that want to use
ii  liblcms1               1.17.dfsg-1       Color management library
ii  libmarble4             4:4.2.0-1         Marble globe widget library
ii  libphonon4             4:4.3.0-2         Phonon multimedia framework for Qt
ii  libpng12-0             1.2.33-2          PNG library - runtime
ii  libqt4-dbus            4.5.0~rc1-2       Qt 4 D-Bus module
ii  libqt4-network         4.5.0~rc1-2       Qt 4 network module
ii  libqt4-qt3support      4.5.0~rc1-2       Qt 3 compatibility library for Qt
ii  libqt4-sql             4.5.0~rc1-2       Qt 4 SQL module
ii  libqt4-sql-sqlite      4.5.0~rc1-2       Qt 4 SQLite 3 database driver
ii  libqt4-svg             4.5.0~rc1-2       Qt 4 SVG module
ii  libqt4-xml             4.5.0~rc1-2       Qt 4 XML module
ii  libqtcore4             4.5.0~rc1-2       Qt 4 core module
ii  libqtgui4              4.5.0~rc1-2       Qt 4 GUI module
ii  libstdc++6             4.3.3-4           The GNU Standard C++ Library v3
ii  libtiff4               3.8.2-11          Tag Image File Format (TIFF) libra
ii  phonon                 4:4.3.0-2         metapackage for Phonon multimedia
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages digikam recommends:
ii  konqueror                     4:4.2.0-1  KDE 4's advanced file manager, web

Versions of packages digikam suggests:
ii  digikam-doc                   0.9.5-1    handbook for digikam and showfoto

-- no debconf information

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #1 from Mark Purcell <msp debian org>  2009-02-26 20:01:52 ---
Also crash report from another user:

Application: digiKam (digikam), signal SIGSEGV
[Current thread is 0 (LWP 18752)]

Thread 4 (Thread 0xb32d7b90 (LWP 18753)):
#0  0xb7fb9424 in __kernel_vsyscall ()
#1  0xb5109025 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb55017fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb56e6852 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0x0828e879 in ?? ()
#5  0xb56e583e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51054c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54f36de in clone () from /lib/i686/cmov/libc.so.6

Thread 3 (Thread 0xb2791b90 (LWP 18755)):
#0  0xb7fb9424 in __kernel_vsyscall ()
#1  0xb5109025 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb55017fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb56e6852 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7206bda in Digikam::LoadSaveThread::run () from
/usr/lib/libdigikamcore.so.1
#5  0xb56e583e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51054c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54f36de in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb1e81b90 (LWP 18756)):
#0  0xb7fb9424 in __kernel_vsyscall ()
#1  0xb5109025 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb55017fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb56e6852 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb7206bda in Digikam::LoadSaveThread::run () from
/usr/lib/libdigikamcore.so.1
#5  0xb56e583e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51054c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54f36de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb483b6c0 (LWP 18752)):
#0  0xb7fb9424 in __kernel_vsyscall ()
#1  0xb54aeef6 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb54aed0f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb6943128 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Gilles Caulier-4
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #2 from Gilles Caulier <caulier gilles gmail com>  2009-02-26 20:10:47 ---
Mark,

Can you run digiKam under gdb to have more informations. Here, i cannot see
where crash appear.

>Versions of packages digikam recommends:
>ii  konqueror                     4:4.2.0-1  KDE 4's advanced file manager, web

=> there is no depency with konqueror in digiKam (:=)))

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Mark Purcell
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #3 from Mark Purcell <msp debian org>  2009-02-26 20:18:35 ---
On Friday 27 February 2009 06:10:48 you wrote:
> Can you run digiKam under gdb to have more informations. Here, i cannot see
> where crash appear.

Gilles,

Unfortunately I cannot reproduce, it works for me, but I will get the two users
who are reporting the issue to run under gdb.

> >Versions of packages digikam recommends:
> >ii  konqueror                     4:4.2.0-1  KDE 4's advanced file
> > manager, web
>
> => there is no depency with konqueror in digiKam (:=

For KDE4.2 this should be changed to dolphin.  As digikam calls dolphin under
the Album:'Open in FileManager' menu entry.

It is only a recommends, so this is the normal case, however the user can
un-install if they wish.

Mark

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Bugzilla from andi.clemens@gmx.net
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #4 from Andi Clemens <andi clemens gmx net>  2009-02-26 20:24:21 ---
Still there is no dependency to konqueror or dolphin. digiKam just has a
services menu, whatever you associate with a certain filetype will be displayed
in there.
If debian packages it that way, it is weird...

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Mark Purcell
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #5 from Mark Purcell <msp debian org>  2009-02-26 20:38:19 ---
(In reply to comment #4)
> Still there is no dependency to konqueror or dolphin. digiKam just has a
> services menu, whatever you associate with a certain filetype will be displayed
> in there.
> If debian packages it that way, it is weird...

For a KDE user this isn't an issue, but there are some digikam users who are
not KDE users.

This has been an issue in the past:
http://bugs.debian.org:80/cgi-bin/bugreport.cgi?bug=440250

Mark

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Mark Purcell
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #6 from Mark Purcell <msp debian org>  2009-02-28 13:56:55 ---
Marble is installed, this is not the issue.  The GDB dump below, confirms
there is an issue: something to do with the undcard. Indeed I confirm
on my laptop, sound is still not working. However I don understand why
Digikam is involved in sound.

Should I involve the Phonon maintainers in this ?

Luc

===========================

Below the GDB dump
======================================================

luc@lanaken:~$ gdb digikam
GNU gdb (GDB) 6.8.50.20090106-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/digikam
(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]
(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)
[New Thread 0xb31efb90 (LWP 3415)]
(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)
[New Thread 0xb26bbb90 (LWP 3416)]
[New Thread 0xb1eb1b90 (LWP 3417)]
[Thread 0xb26bbb90 (LWP 3416) exited]
(no debugging symbols found)
[Thread 0xb1eb1b90 (LWP 3417) exited]
[New Thread 0xb1eb1b90 (LWP 3422)]
[New Thread 0xb26bbb90 (LWP 3423)]
(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)
digikam(3404) Phonon::KdePlatformPlugin::createBackend: using backend:  
"GStreamer"
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) "Cirrus Logic CS4281 (CS4281)"
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) ("x-phonon:CARD=0,DEV=0",
"plughw:CARD=0,DEV=0")          
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) setProperty(device, "x-phonon:CARD=0,DEV=0"
) failed      
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) setProperty(device, "plughw:CARD=0,DEV=0" )
failed        
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) "Cirrus Logic CS4281 (CS4281)"
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) ("x-phonon:CARD=0,DEV=0",
"plughw:CARD=0,DEV=0")          
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) setProperty(device, "x-phonon:CARD=0,DEV=0"
) failed      
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) setProperty(device, "plughw:CARD=0,DEV=0" )
failed        
virtual bool Phonon::Gstreamer::AudioOutput::setOutputDevice(const
Phonon::AudioOutputDevice&) "default"

Program received signal SIGSEGV, Segmentation fault.
0xb5812677 in QMetaObject::activate(QObject*, QMetaObject const*, int,
void**) () from /usr/lib/libQtCore.so.4
(gdb) thread apply all backtrace

Thread 6 (Thread 0xb26bbb90 (LWP 3423)):
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb5125fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb5520f2d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb5709852 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4  0xb7228bda in Digikam::LoadSaveThread::run() () from
/usr/lib/libdigikamcore.so.1
#5  0xb570883e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51224e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb551210e in clone () from /lib/i686/cmov/libc.so.6

Thread 5 (Thread 0xb1eb1b90 (LWP 3422)):
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb5125fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb5520f2d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb5709852 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4  0xb7228bda in Digikam::LoadSaveThread::run() () from
/usr/lib/libdigikamcore.so.1
#5  0xb570883e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51224e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb551210e in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb31efb90 (LWP 3415)):
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb5125fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb5520f2d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb5709852 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQtCore.so.4
#4  0x0828e879 in ?? ()
#5  0xb570883e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51224e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb551210e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4841700 (LWP 3404)):
#0  0xb5812677 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/libQtCore.so.4
#1  0xb7f87423 in ?? () from /usr/lib/libphonon.so.4
#2  0x00000000 in ?? ()
(gdb)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Gilles Caulier-4
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638





--- Comment #7 from Gilles Caulier <caulier gilles gmail com>  2009-02-28 14:01:18 ---
This is another prblem with KDE technologies: Phonon require libxine, which
have some problem currently. try to update libxine...

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Gilles Caulier-4
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |xine backend
            Version|0.10.0-rc2                  |4.1 (Qt 4.4)
            Product|digikam                     |Phonon




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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 185638] digikam crash on startup

Gilles Caulier-4
In reply to this post by Mark Purcell
https://bugs.kde.org/show_bug.cgi?id=185638


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|xine backend                |gstreamer backend
            Version|4.1 (Qt 4.4)                |4.2 (KDE 4.1)
         AssignedTo|[hidden email]       |[hidden email]




--- Comment #8 from Gilles Caulier <caulier gilles gmail com>  2009-02-28 14:14:10 ---
Mark,

File is reassigned to Phonon. sound like it's a GStreamer problem relevant.

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- 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