Cannot save image edits to NAS with dK 1.0.0 beta 5

[Duffields]

On one of my computers I use digKam 0.9.3 with Ubuntu 8.04 and it works great!
My only complaint is that this version of digiKam cannot work with network
files so I have to create a symbolic link from a local directory to the
network files which are located on a D-link DNS-323, and I cannot have more
than one collection.  

With the release of Ubuntu 9.10, I installed it on another computer (which has
a faster processor) and installed digiKam 1.0.0 beta 5 from the Ubuntu
repositories.

digiKam's new ability to work with external files is a welcome change, thank
you,  but I have found two problems, one of them serious:

1.  I cannot save images edited with digiKam on the NAS.  When I attempt to
save an image I get an error message such as the following example:

"Error digiKam
Failed to save file
Racoon2 Crop.jpg
To
"/media/RAID/Photos/Creatures/Racoon2 Crop.jpg""

The NAS files are auto-mounted at start-up through an entry in fstab and the
mount point is "/media/RAID/Photos"

I have tried to edit and save a file using GIMP and that works so I assume the
problem lies within digiKam.

2. The second problem is not as severe, but when digiKam starts on this
computer the scan time to bring up the same set of images from the time the
splash screen appears to the time the first image screen appears is 57
seconds.  This is after the initial scan associated with the new
installation.

On digikam 0.9.3, the time from when the scan screen first appears until the
first image screen appears is 10 seconds.  And this is on a slower computer.

Can anyone shine any light on either of these issues?  
I am particularly concerned about not being able to save edits with digiKam
1.0.0.

Thanks
Mac
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

Hi,

for both issues I would ask if there is debug output on the console (enable
code 50003 with kdebugdialog before).
I recommend you to open two bugs in bugs.kde.org, follow-up tends to be lost
on the command line.

Marcel

> With the release of Ubuntu 9.10, I installed it on another computer (which
>  has a faster processor) and installed digiKam 1.0.0 beta 5 from the Ubuntu
>  repositories.
>
> digiKam's new ability to work with external files is a welcome change,
>  thank you,  but I have found two problems, one of them serious:
>
> 1.  I cannot save images edited with digiKam on the NAS.  When I attempt to
> save an image I get an error message such as the following example:
>
> "Error digiKam
> Failed to save file
> Racoon2 Crop.jpg
> To
> "/media/RAID/Photos/Creatures/Racoon2 Crop.jpg""
>
> The NAS files are auto-mounted at start-up through an entry in fstab and
>  the mount point is "/media/RAID/Photos"
>
> I have tried to edit and save a file using GIMP and that works so I assume
>  the problem lies within digiKam.
>
> 2. The second problem is not as severe, but when digiKam starts on this
> computer the scan time to bring up the same set of images from the time the
> splash screen appears to the time the first image screen appears is 57
> seconds.  This is after the initial scan associated with the new
> installation.
>
> On digikam 0.9.3, the time from when the scan screen first appears until
>  the first image screen appears is 10 seconds.  And this is on a slower
>  computer.
>
> Can anyone shine any light on either of these issues?
> I am particularly concerned about not being able to save edits with digiKam
> 1.0.0.
>
> Thanks
> Mac
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Marcel Wiesweg]

> >for both issues I would ask if there is debug output on the console
> > (enable code 50003 with kdebugdialog before).
>
> I do not run digiKam from the consol.  Is there another "consol" that I
>  should be looking for or enabling for a debug procedure?

Type Alt+F2. Enter "kdebugdialog". In the search bar, type 50003. Ensure there
is a full check mark for digikam and press ok.
Type Alt+F2. Enter "konsole". In the opening terminal, enter "digikam" and
press enter. Digikam starts. You will see quite a few messages appearing. The
interesting ones are those that appear while you trigger the actions that
cause errors for you. Please copy them to your bug report.

>
> >I recommend you to open two bugs in bugs.kde.org, follow-up tends to be
> > lost on the command line.
>
> I have never filed bugs in bugs.kde.org,  but I assume there are
>  instructions somewhere on the site.

The easiest way is to open digikam, and in the "Help" menu, select "Report
bug". This will lead you to the bugs.kde.org website. In this case here you
can skip the searching of existing reports, just fill your problem description
as in this mail.

Marcel
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users