Bug 194925 - error "the process for the digikamalbums protocol died unexpectedly"
Summary: error "the process for the digikamalbums protocol died unexpectedly"
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Albums (show other bugs)
Version: 0.10.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-01 23:04 UTC by Gregor B. Rosenauer
Modified: 2017-07-19 13:58 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.5.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor B. Rosenauer 2009-06-01 23:04:05 UTC
Version:           0.10.0 (using 4.2.2 (KDE 4.2.2), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.29-4.slh.4-sidux-amd64

When trying to copy photos from a local album to a network album, I always get the error in the subject line:
"the process for the digikamalbums protocol died unexpectedly"
(German:
"Der Prozess für das Protokoll digikamalbums wurde unerwartet beendet.")

AutoSkip however works fine and all photos are copied OK.
What does the error mean and why does it occur?

I can copy/move photos fine both within my network and within my local album, but not across albums/network borders it seems.

The network album is shared using a Debian Samba server (latest stable 3.x).
Comment 1 Vitalii Tymchyshyn 2009-10-18 21:49:46 UTC
Same for me for 1.0beta5 
My network storage is NFS-mounted (in fstab).
My OS is Opensuse with KDE 4.3.1-169.1 from KDE4 - Factory - Desktop
Comment 2 caulier.gilles 2011-12-15 10:14:15 UTC
Rosenauer,

This file still valid using digiKam 2.x serie ?

Gilles caulier
Comment 3 Gregor B. Rosenauer 2011-12-15 23:08:27 UTC
didn't see this again, just manually copied photos from my USB stick to a network album (samba), no problems with digikam 2.4.2.
Comment 4 julien.t43+kde 2012-07-25 17:15:52 UTC
Got this problem in 2.7 with lubuntu 12.04/ppa. logout/login (aka restart kde) solves the problem and it seems whole kde was affected as KDE Crash handler also had some strange similar behavior.
Probably those are related bug 227498 - 194925.
Comment 5 Peter Gervai 2015-05-17 09:14:41 UTC
You don't really have to restart the system, just kill off old kdeinit4 instances.
$ killall kdeinit4
(Sometimes it doesn't get all killed, you may want to look in 'ps'.)

This, by the way, sucks. Absolutely user unfriendly. And if I didn't know what causes it it would be really close to impossible to fix, and rebooting to fix something is so windowsey....
Comment 6 caulier.gilles 2015-05-17 09:43:37 UTC
Note : For KF5 port of digiKam all kioslaves will be replaced by an multithreaded interface. It's a GSoC 2015 project.

So this problem will not happen anymore in the future.

Gilles Caulier