Been happening awhile, probably since I started using beta 4.5(?) but it works fine for root. If I rebuild thumbs (under tools, I see all the images with thumbs being processed) but still no thumbnails in the album window.

digikam(18305)/digikam (core) Digikam::ImageAlbumModel::slotResult: Failed to list url: "Could not start process Unable to create io-slave:
klauncher said: Error loading 'kio_digikamalbums'.

running digikam digikam-1.3.0-70.3.x86_64, under kde4.5 beta2, openSuse 10.2


Tried renaming rc file and apps/digikam directory but same issue

thanks,

KLauncher's error message is likely key to this....
Have you tried running "kbuildsycoca4 --noincremental"?

bcooksley wrote:KLauncher's error message is likely key to this....
Have you tried running "kbuildsycoca4 --noincremental"?

did as you suggested but did not resolve it - same error messages

Can you please run "kdebugdialog", and enable all areas? After that, trigger the issue and check ~/.xsession-errors for messages from KLauncher as to why it is failing to launch this KIO slave.

bcooksley wrote:Can you please run "kdebugdialog", and enable all areas? After that, trigger the issue and check ~/.xsession-errors for messages from KLauncher as to why it is failing to launch this KIO slave.

Could not open library '/usr/lib64/kde4/kio_digikamdates.so'.
Cannot load library /usr/lib64/kde4/kio_digikamdates.so: (/usr/lib64/libphonon.so.4: symbol pa_ext_device_manager_reorder_devices_for_role, version PULSE_0 not defined in file libpulse.so.0 with link time reference)
Could not open library '/usr/lib64/kde4/kio_digikamalbums.so'.
Cannot load library /usr/lib64/kde4/kio_digikamalbums.so: (/usr/lib64/libphonon.so.4: symbol pa_ext_device_manager_reorder_devices_for_role, version PULSE_0 not defined in file libpulse.so.0 with link time reference)
===============================

could this be related to this http://der-dakon.net/blog/KDE/who-broke ... honon.html? which would make it a openSuse packaging problem?

posted bug report to Suse Bugzilla https://bugzilla.novell.com/show_bug.cgi?id=613534

Yes it is very likely related to that packaging error.