[packman] OpenShot no longer starts up

[Willem Franssen]

Dear Packman Team,

System: OpenSUSE 12.1+KDE 4.7.2  x86

OpenShot 1.4.0-1.3 all of a sudden no longer starts up after updating 
several packman-packages.
Error-output:

linux-5al1:/home/Wimmie # openshot

------------------------- ERROR 1 ------------------------------
Failed to import 'from openshot import main'
Error Message: cannot import name main
----------------------------------------------------------------
--------------------------------
    OpenShot (version 1.4.0)
--------------------------------

(gst-plugin-scanner:2658): GLib-GObject-CRITICAL **: 
g_param_spec_double: assertion `default_value >= minimum && 
default_value <= maximum' failed

(gst-plugin-scanner:2658): GLib-GObject-CRITICAL **: 
g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed

(gst-plugin-scanner:2659): GLib-GObject-CRITICAL **: 
g_param_spec_double: assertion `default_value >= minimum && 
default_value <= maximum' failed

(gst-plugin-scanner:2659): GLib-GObject-CRITICAL **: 
g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed

(gst-plugin-scanner:2660): GStreamer-WARNING **: Failed to load plugin 
'/usr/lib/gstreamer-0.10/libgstdc1394.so': 
/usr/lib/gstreamer-0.10/libgstdc1394.so: undefined symbol: 
dc1394_iso_release_all

(gst-plugin-scanner:2660): GConf-WARNING **: Client failed to connect to 
the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, 
the reply timeout expired, or the network connection was broken.

(gst-plugin-scanner:2660): GConf-WARNING **: Client failed to connect to 
the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, 
the reply timeout expired, or the network connection was broken.

(gst-plugin-scanner:2660): GConf-WARNING **: Client failed to connect to 
the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, 
the reply timeout expired, or the network connection was broken.

(gst-plugin-scanner:2660): GConf-WARNING **: Client failed to connect to 
the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application 
did not send a reply, the message bus security policy blocked the reply, 
the reply timeout expired, or the network connection was broken.
GConf Fout: No D-BUS daemon running

Segmentatiefout

What can be wrong?

Kind regards,
Willem Franssen