reassign 560893 libmarble4 4:4.3.4-1
affects 560893 digikam
tag 560893 upstream fixed-upstream
thanks
On Thursday 31 December 2009 18:00:55 Dietz Pröpper wrote:
I suspect this issue is being caused by the marble plugin widget in
digikam.
I second that. Downgrading marble to the version
Processing commands for cont...@bugs.debian.org:
reassign 560893 libmarble4 4:4.3.4-1
Bug #560893 [digikam] digikam: digicam eats all cpu
Bug reassigned from package 'digikam' to 'libmarble4'.
Bug No longer marked as found in versions digikam/2:1.0.0~rc-1.
Bug #560893 [libmarble4] digikam:
Package: digikam
Version: 2:1.0.0-1
Severity: grave
Justification: renders package unusable
After updating from digikam 2:1.0.0~beta4-2 to digikam 2%3a1.0.0-1_i386.deb
from unstable, digikam does not show any images anymore in my collection. All
folders show (0) images. The problem remains
#
# bts-link upstream status pull for source package digikam
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #551535 (http://bugs.debian.org/551535)
# *
Processing commands for cont...@bugs.debian.org:
#
# bts-link upstream status pull for source package digikam
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org
On Tuesday 05 January 2010 02:41:18 datenritter wrote:
After updating from digikam 2:1.0.0~beta4-2 to digikam 2%3a1.0.0-1_i386.deb
from unstable, digikam does not show any images anymore in my collection.
All folders show (0) images. The problem remains after deleting the
database files and
