Opened 10 years ago

Closed 9 years ago

#28308 closed defect (fixed)

Digikam displays no images: "unable to create io-slave"

Reported by: sk-public@… Owned by: jgosmann (Jan Gosmann)
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: io-slave kio_digikamalbums Cc: m214089, kea@…
Port: digikam

Description

With a clean build of digikam 1.8.0, digikam launches but doesn't display any images, complaining of an inability to load kio_digikamalbums and kio_digikamdates.

$ /opt/digikam1.8/var/macports/software/digikam/1.8.0_0+geoloc+kipi/opt/digikam-1.8/Applications/KDE4/digikam.app/Contents/MacOS/digikam 
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work 
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
Time elapsed: 60 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
Time elapsed: 13 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
digikam(841)/KIPI (general) Plugin_DebianScreenshots::setup: virtual void Plugin_DebianScreenshots::setup(QWidget*) 
Time elapsed: 14 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
Time elapsed: 14 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
Time elapsed: 14 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
digikam(841)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::ImagePropertiesSideBarDB(0x14f816af0)  is empty. Returning the default config group 
digikam(841)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::ImagePropertiesSideBarDB(0x150cc9730)  is empty. Returning the default config group 
kdeinit4: (kio_digikamdates ) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
digikam(841): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamdates'.
" 
digikam(841)/digikam (core) Digikam::AlbumManager::slotDatesJobResult: Failed to list dates 
kdeinit4: (kio_digikamalbums ) Pipe closed unexpectedlykdeinit4: Pipe closed unexpectedly: No such file or directory
digikam(841): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
" 
digikam(841)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to list url:  "Could not start process Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
." 

These files (kio_digikamalbums, kio_digikamdates) do exist, in /opt/digikam-1.8/lib/kde4 and /opt/digikam-1.8/var/macports/software/digikam/1.8.0_0+geoloc+kipi/opt/digikam-1.8/lib/kde4/ from the macports install directory.

Permissions on ~/Library/Preferences/KDE have been set. I've removed and recreated ~/Library/Preferences/KDE/shares, and removed /var/tmp/kdecache-$USER. I've set LDPATH to the directory where they are found. It doesn't change the result.

Change History (17)

comment:1 Changed 10 years ago by jmroot (Joshua Root)

Owner: changed from macports-tickets@… to jan@…

Please remember to cc the maintainer.

comment:2 Changed 10 years ago by m214089

Got hit by the same problem after upgrading (port upgrade outdated).

comment:3 Changed 10 years ago by m214089

Cc: luis.kornblueh@… added

Cc Me!

comment:4 Changed 10 years ago by j.stroettchen@…

Same problem here. Digikam 1.8 runs smoothly on top of the KDE-4.5.3 stuff. After compiling kdepimlibs -edu and -graphics on top of kdelibs 4.5.3 digikam 1.8 still works. As soon as kdelibs 4.6.0 show up the annoying "Error loading 'kio_digikamalbums" drops in ...

comment:5 Changed 10 years ago by j.stroettchen@…

Sorry: " after compiling kdepimlibs -edu -graphics (4.6.0) on top of kdelibs 4.5.3"

comment:7 Changed 10 years ago by kea@…

Cc Me!

comment:8 Changed 10 years ago by kea@…

Cc: kea@… added

Cc Me!

comment:9 Changed 10 years ago by jgosmann (Jan Gosmann)

I forwarded this bug to the KDE/Digikam bug tracker: https://bugs.kde.org/show_bug.cgi?id=266735

However, I was not able to verify this bug, because for me Digikam does not even start. :( (I also reported that problem: https://bugs.kde.org/show_bug.cgi?id=266733)

@carcode: You should include logs in three curly braces to get a readable formatting.

comment:10 Changed 10 years ago by carcode@…

@jan: Sorry for that unreadable log. When I see that for myself there was no way found by me to edit my post.

Yes, Digikam starts here (compiled with all needed depencies a few days ago), but it complaints about the "kio_digikamalbums". May be there is a missing or wrong setting anywhere but I do not know where to search for. And why does kdeinit4 crashes? All other KDE apps works without any problems here.

comment:11 in reply to:  description ; Changed 10 years ago by apple@…

Cc Me!

comment:12 in reply to:  11 Changed 10 years ago by apple@…

Replying to apple@…: Here is the log from running a compiled version of the 1.9 release that I just downloaded (on a Mac-Mini 64 bit OSX 10.6):

curry$ /Applications/KDE4/digikam.app/Contents/MacOS/digikam ; exit;
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work 
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
Time elapsed: 55 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 6 ms
Time elapsed: 36 ms
Model: Time elapsed: 0 ms
No location could be retrieved for url  QUrl( "file:" )  
digikam(56290)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for  "" 
TextureColorizer::setSeaFileLandFile: Time elapsed: 6 ms
QFSFileEngine::open: No file name specified
digikam(56290)/KIPI (general) Plugin_DebianScreenshots::setup: virtual void Plugin_DebianScreenshots::setup(QWidget*) 
digikam(56290)/digikam (core) Digikam::ImagePluginLoader::loadPluginsFromList: ImagePluginLoader: createInstance returned 0 for  "ImagePlugin_Color"  ( "digikamimageplugin_color" )  with error:  "The service 'ImagePlugin_Color' does not provide an interface 'Digikam::ImagePlugin' with keyword ''" 
digikam(56290)/digikam (core) Digikam::ImagePluginLoader::loadPluginsFromList: ImagePluginLoader: createInstance returned 0 for  "ImagePlugin_Decorate"  ( "digikamimageplugin_decorate" )  with error:  "The service 'ImagePlugin_Decorate' does not provide an interface 'Digikam::ImagePlugin' with keyword ''" 
digikam(56290)/digikam (core) Digikam::ImagePluginLoader::loadPluginsFromList: ImagePluginLoader: createInstance returned 0 for  "ImagePlugin_Enhance"  ( "digikamimageplugin_enhance" )  with error:  "The service 'ImagePlugin_Enhance' does not provide an interface 'Digikam::ImagePlugin' with keyword ''" 
digikam(56290)/digikam (core) Digikam::ImagePluginLoader::loadPluginsFromList: ImagePluginLoader: createInstance returned 0 for  "ImagePlugin_FxFilters"  ( "digikamimageplugin_fxfilters" )  with error:  "The service 'ImagePlugin_FxFilters' does not provide an interface 'Digikam::ImagePlugin' with keyword ''" 
digikam(56290)/digikam (core) Digikam::ImagePluginLoader::loadPluginsFromList: ImagePluginLoader: createInstance returned 0 for  "ImagePlugin_Transform"  ( "digikamimageplugin_transform" )  with error:  "The service 'ImagePlugin_Transform' does not provide an interface 'Digikam::ImagePlugin' with keyword ''" 
Time elapsed: 13 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
Time elapsed: 14 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 6 ms
Time elapsed: 12 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 7 ms
digikam(56290)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::ImagePropertiesSideBarDB(0x14d0c1770)  is empty. Returning the default config group 
digikam(56290)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::ImagePropertiesSideBarDB(0x14fe6aa70)  is empty. Returning the default config group 
digikam(56290): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamdates'.
" 
digikam(56290)/digikam (core) Digikam::AlbumManager::slotDatesJobResult: Failed to list dates 
digikam(56290): couldn't create slave: "Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
" 
digikam(56290)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to list url:  "Could not start process Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.
." 
QFSFileEngine::open: No file name specified
digikam(56290)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::Sidebar(0x14fe6aa70)  is empty. Returning the default config group 
digikam(56290)/digikam (core) Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for  Digikam::Sidebar(0x14d0c1770)  is empty. Returning the default config group 
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-4418411904' is still in use, all queries will cease to work.
logout

[Process completed]


comment:13 Changed 10 years ago by carcode@…

So who is responsible now? Are this the MacPorts people, the KDE people or the Digikam people? It seems to me that nobody cares about and each group thinks it might be the fault of the other group. Very frustating...

comment:14 Changed 10 years ago by jgosmann (Jan Gosmann)

I would say the Digikam and/or KDE people are responsible. I started creating the portfiles for Digikam and kipi-plugins because those were missing within Macports and it is not that much work. But I do not really have knowledge about the Digikam source code and stuff like that. Therefore it would be probably hard for me to fix this. That's the reason I filed a bug in the KDE bug tracker (which includes Digikam).

Moreover, the problem with Digikam not starting on my machine is still unsolved (Digikam says it cannot find a file, but that file exists and is accessible).

comment:15 in reply to:  14 Changed 10 years ago by apple@…

Replying to jan@…:

I would say the Digikam and/or KDE people are responsible. I started creating the portfiles for Digikam and kipi-plugins because those were missing within Macports and it is not that much work. But I do not really have knowledge about the Digikam source code and stuff like that. Therefore it would be probably hard for me to fix this. That's the reason I filed a bug in the KDE bug tracker (which includes Digikam).

Moreover, the problem with Digikam not starting on my machine is still unsolved (Digikam says it cannot find a file, but that file exists and is accessible).

This problem seems to have been resolved with kdelibs4 4.6.1.

comment:16 Changed 10 years ago by jgosmann (Jan Gosmann)

Indeed. Digikam shows the images again after installing kdelibs4 4.6.1.

comment:17 Changed 10 years ago by sk-public@…

Works for me as also, after update to kdelibs4 4.6.1.

comment:18 Changed 9 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.