Bad behavior with unreadable files
Submitted by Pedro Villavicencio
Link to original bug (#606628)
Description
totem version is : 2.29.2
this report has been filed here:
https://bugs.edge.launchpad.net/ubuntu/+source/totem/+bug/505065
"If a user does not have read permissions for a file s/he is trying to open, while it is already playing something, Totem becomes unresponsive to his/her commands until it is closed and restarted.
Prerequisites:
- Have the package example-content installed, or two media files of your choosing.
- Designate one as ReadableFile. Make sure it's readable (chown me:me ReadableFile; chmod u+r ReadableFile).
- Designate one as UnreadableFile. Make sure it's NOT readable (chown root:root UnreadableFile; chmod o-rwx UnreadableFile).
Steps to reproduce:
- Open Totem.
- Menu File/Open, choose ReadableFile.
- Menu File/Open, choose UnreadableFile.
- Four dialog boxes appear on top of each other, each saying the same thing about an unreadable file. (Expected: one dialog is enough ;)
- Menu File/Open, choose ReadableFile.
- Nothing happens. (Expected: ReadableFile starts playing again)
This also happens if the File menu's recent entries are used to play UnreadableFile."
Version: 2.29.x