Comment 7 for bug 349467

For those who installed the bad package before canonical 403'd it, please use a terminal and enter "sudo apt-get update" followed by "sudo apt-get upgrade".

If you have the broken python package you will likely also see crashes in many other applications. For example, when I run totem I get this SEGV:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa4805d07f0 (LWP 4447)]
0x000000000044f8a4 in totem_python_module_load (gmodule=0x28fc980) at /build/buildd/totem-2.26.0/src/plugins/totem-python-module.c:282
282 /build/buildd/totem-2.26.0/src/plugins/totem-python-module.c: No such file or directory.
 in /build/buildd/totem-2.26.0/src/plugins/totem-python-module.c
(gdb) bt
#0 0x000000000044f8a4 in totem_python_module_load (gmodule=0x28fc980) at /build/buildd/totem-2.26.0/src/plugins/totem-python-module.c:282
#1 0x00007fa47b1ecef4 in IA__g_type_module_use (module=0x28fc980) at /build/buildd/glib2.0-2.20.0/gobject/gtypemodule.c:257
#2 0x000000000044cf9d in totem_plugins_engine_activate_plugin (info=0x29a5f80) at /build/buildd/totem-2.26.0/src/plugins/totem-plugins-engine.c:533
#3 0x000000000044d7bd in totem_plugins_engine_load_dir (path=0x29a8010 "/usr/lib/totem/plugins/bbc")
    at /build/buildd/totem-2.26.0/src/plugins/totem-plugins-engine.c:318
#4 0x000000000044d3a0 in totem_plugins_engine_load_dir (path=0x29b2710 "/usr/lib/totem/plugins")
    at /build/buildd/totem-2.26.0/src/plugins/totem-plugins-engine.c:336
#5 0x000000000044d978 in totem_plugins_engine_init (totem=<value optimized out>)
    at /build/buildd/totem-2.26.0/src/plugins/totem-plugins-engine.c:352
#6 0x0000000000421538 in main (argc=1, argv=0x7fff8861fa08) at /build/buildd/totem-2.26.0/src/totem.c:255
(gdb)