15 Sep
2012
15 Sep
'12
11:44 p.m.
On Mon, Sep 3, 2012 at 6:41 PM, Darrell Anderson <humanreadable(a)yahoo.com>wrote;wrote:
Time for a new thread.
I have been beating myself up hard today troubleshooting some of the TDEHW
quirks I have been reporting.
I believe we have two separate problems.
One is the "eject -T dvd" command stops working as soon as a disk is
inserted. From what I gather online, this is a known bug and there is a
patch. I haven't looked for the patch or tested.
I verified the "eject -T" problem exists in Xfce 4.10 and KDE 4.8.5 too.
Thus, "eject -T" is broken one way or another.
The second problem is permissions. As root I tested Safely Remove with USB
flash drives and Eject with an optical disk. The icons disappear for both,
and the optical disk physically ejects. Although after the disk ejects the
"eject -T dvd" command stops working until after I use the drive eject
button. Then the "eject -T" command works.
I can't figure out what the permissions problem might be. I don't see any
special suid permissions on any of the TDE bin files or the eject command.
Could the TDEHW code cause this behavior?
Could pmount be causing this behavior? I never have used pmount before so
I am a complete noob.
Is there any validation process in place before releases? It seems to me
that even tough it is important to have functionality like this working
perfectly, current hardware is moving away from optical drives and this may
not be tested extensively before a release.
Thoughts?
Best regards,
Tiago
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting