GNOME Bugzilla – Bug 606628
Bad behavior with unreadable files
Last modified: 2018-05-24 10:37:15 UTC
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: 1. Have the package example-content installed, or two media files of your choosing. 2. Designate one as ReadableFile. Make sure it's readable (chown me:me ReadableFile; chmod u+r ReadableFile). 3. Designate one as UnreadableFile. Make sure it's NOT readable (chown root:root UnreadableFile; chmod o-rwx UnreadableFile). Steps to reproduce: 1. Open Totem. 2. Menu File/Open, choose ReadableFile. 3. Menu File/Open, choose UnreadableFile. 4. Four dialog boxes appear on top of each other, each saying the same thing about an unreadable file. (Expected: one dialog is enough ;) 5. Menu File/Open, choose ReadableFile. 6. Nothing happens. (Expected: ReadableFile starts playing again) This also happens if the File menu's recent entries are used to play UnreadableFile."
I can confirm this... for me is reproducible. I Change status to NEW.
I reported this bug to Ubuntu in Launchpad; I was about to file it here after seeing that the issue was upstream, but then saw that the thread also had Pedro filing it here. Since this originally affected me, I'm confirming this too.
I can't get it to hang, but the play status gets in a bad state after dismissing the (single ;) error dialogue and clicking on "Play", so let's try and fix that.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/totem/issues/37.