[intrepdi] digikam is running 100% cpu at start

Bug #275559 reported by Schmirrwurst
2
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Invalid
Undecided
Unassigned
Nominated for Intrepid by Schmirrwurst

Bug Description

Binary package hint: digikam

When starting digikam, it is staying on scan albums for hours, taking 100% of cpu...
I haven't found something interesting by starting it from the command line :
digikam(9563): Root Album Path: ""
digikam(9563): Database Path: "/home/ttt/Images"
digikam(9563): SchemaUpdater update
digikam(9563): Have a database structure version "5"
digikam(9563): makeUpdates 5 to 5
digikam(9563): listFromType
digikam(9563): got listFromType
digikam(9563): Creating new Location "/" uuid "volumeid:?path="
digikam(9563): location for "/" is available true

Revision history for this message
Marc Argent (lurcio) wrote :

I have tried digikam on Intrepid with 2 gigabytes of random images in my Pictures folder, but it only uses about 50% of the CPU for under 30 seconds. How can I reproduce the bug?

Is any other disk IO occurring at the same time? Perhaps backup software, anti virus scanning or some desktop search tool indexing files? Is the hard disk functioning well? If you look in /var/log/messages are there messages complaining about bad blocks?

Revision history for this message
Schmirrwurst (schmirrwurst) wrote : Re: [Bug 275559] Re: [intrepdi] digikam is running 100% cpu at start

No, I haven't anything else running at the same time. There are no input in
/var/log/messages
I've tried to delete the db... and re-run digikam, with the same effect...

On Monday 29 September 2008 13:13:36 Marc Argent wrote:
> I have tried digikam on Intrepid with 2 gigabytes of random images in my
> Pictures folder, but it only uses about 50% of the CPU for under 30
> seconds. How can I reproduce the bug?
>
> Is any other disk IO occurring at the same time? Perhaps backup
> software, anti virus scanning or some desktop search tool indexing
> files? Is the hard disk functioning well? If you look in
> /var/log/messages are there messages complaining about bad blocks?

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

I've also tried to delete configuration file, with the same effect.....

Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

deleting the complete .kde configuration directory solved the problem...

Changed in digikam:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.