Thanks Luc,
I have forwarded upstream.
https://bugs.kde.org/show_bug.cgi?id=185638#c6
On Saturday 28 February 2009 23:49:10 you wrote:
Should I involve the Phonon maintainers in this ?
It is in the kde bugtracker now, so they should be able to reassign as
necessary.
Mark
signature.asc
http://bugs.debian.org/491458
Luc, Martial,
Can you confirm you are running with libxine 1.1.16.1-2?
dpkg -l libxine* | grep ^i
ii libxine-dev 1.1.16.1-2
ii libxine1 1.1.16.1-2
ii libxine1-bin
Mark Purcell schreef:
http://bugs.debian.org/491458
Luc, Martial,
Can you confirm you are running with libxine 1.1.16.1-2?
yes, 100% match!
Luc
dpkg -l libxine* | grep ^i
ii libxine-dev 1.1.16.1-2
ii libxine1
I demand that Luc Castermans may or may not have written...
Mark Purcell schreef:
http://bugs.debian.org/491458
Luc, Martial,
Can you confirm you are running with libxine 1.1.16.1-2?
1.1.16.2-1 is in unstable...
[snip]
--
| Darren Salt| linux or ds at | nr. Ashington, |
Luk, Martial,
I think I have narrowed down this issue.
digikam tries to load the marble plugins, but they are not shipped in the
libmarble package, rather the marble package itself.
The solution is for digikam to Depend on marble, but as a work around, you
should be able to install marble
Luc, Martial,
I have forwarded your crash reports upstream.
Could I ask you to make a backtrace using GDB as follows:
# gdb digikam
run
...
_crash here_
...
bt
_the backtrace is here_
quit
For a detailed and very helpful guide on providing useful crash reports see
this guide
