http://qa.mandrakesoft.com/show_bug.cgi?id=20


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.4.21-1mdk                 |2.4.22-0.7mdk




------- Additional Comments From [EMAIL PROTECTED]  2003-29-08 16:07 -------
This bug has been automatically updated to last version of product available. 

Please check if it is still valid.


------- Additional Comments From [EMAIL PROTECTED]  2003-20-10 23:18 -------
I have tested couple of different drives and IMHO LG's donest have that problem.
I've encountered problem on Lite-On 24x CD-RW and Pioneer DVD-121 DVD-ROM.
Disableing supermount shortens time needed to detect that there is no medina in
drive but it doesn't solve the problem. I still get 23 seconds on Pioneer
compared to immediate response to LG-8480B 48x CD-RW. I have also tried it in
windows and same problem there so maybe it is a hardware issue. Maybe it can be
solved somehow in mount/supermount? It is not rpmdrake issue in my opinion.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date: 
description: 
While adding, removing, or updating sources in the software updater, the CD-ROM
drive is frequently checked.  If the CD-ROM is empty and supermount is enabled,
the CD is tested and takes approximately 1-2 minutes to be recognized as empty
before the software manager continues.  This can be observed on the CD drive
from the light.  When this situation occurs, the Software Manager appears to the
user to have "locked up" and becomes unresponsive.

The temporary workaround is to have a CD (any CD, including an audio CD, which
is what I do) in the drive.  The seek on the drive will drp to 1-2 seconds and
the software manager will appear to work.

I'm not sure where the specific problem lies, but I think it may have to do with
the fact that when adding or removing sources (urmpi), all of the currently
defined sources appear to be checked.  In reality, adding or removing should not
check everything else, simply add or remove.

Reply via email to