Comment 32 for bug 424864

Revision history for this message
James Lewis (james-fsck) wrote :

When I initially logged this problem it was caused when you upgraded, rather than did a fresh install.... Clearly it is related to a configuration parameter which is held over from an older version of Totem. Can I ask anyone who has this problem to either create a new user which has not existed before, and test Totem when logged in with that username, or to close totem, delete/move aside their .gconf/apps/totem folder and test.

Hopefully this will show that when totem starts with no-pre existing configuration this problem does not happen.

Note that you may need to reboot or re-start X to reset the initial state before testing otherwise your result may be a false positive.