Bad behavior with unreadable files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Totem |
Expired
|
Medium
|
|||
totem (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: totem
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.
ProblemType: Bug
Architecture: amd64
Date: Sat Jan 9 05:12:57 2010
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
Package: totem 2.28.4-0ubuntu4
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: totem
Tags: lucid
Uname: Linux 2.6.32-7-generic x86_64
Changed in totem: | |
status: | Unknown → Confirmed |
Changed in totem: | |
importance: | Unknown → Medium |
Changed in totem: | |
status: | Confirmed → In Progress |
Changed in totem: | |
status: | In Progress → Expired |
Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME)