Bug 157537

Summary: yast2 does not umount CDs after installation
Product: [openSUSE] SUSE Linux 10.1 Reporter: Matthias Hopf <mhopf>
Component: YaST2Assignee: Jiri Srain <jsrain>
Status: RESOLVED DUPLICATE QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: suse-beta
Version: Beta 7   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Matthias Hopf 2006-03-13 11:18:09 UTC 
Freshly installed SL10.1b7 (no update) from CD set. KDE, C/C++ development, advanced user as selection. KDE is running.

After installation I started Yast2, Software Management. I want to install libsvg, libsvg-cairo, gconf-editor, control-center2. This results (AFAIR) in 11 packages from CD2 and 2 from CD5 to be installed.

Now when CD5 is to be inserted, the drive does not open when I push the unload button of the drive or if I press the eject button of the dialog. mount shows that the disk is still mounted on /var/adm/mount/AP_xxxxx. I had to manually umount the drive. After inserting the new CD it is automatically mounted. Impossible to do for a regular user.

Machine is gkar, ssh is open, CD 5 is in the drive. I have to do some tests on the machine, though, so it could crash on rare occasions.
Comment 1 Michael Gross 2006-03-13 11:46:24 UTC 
Please attach the yast logfiles.
Comment 2 Michael Gross 2006-03-14 11:10:50 UTC 
Lowering severity, this is not a blocker, because normal operation can be regained easily.
Comment 3 Matthias Hopf 2006-03-14 16:46:03 UTC 
Yast2 logfiles are in attachment #72622 [details] from bug #157535.

IMHO this *is* a blocker, because a normal user cannot remove the CD any more. As I said, the eject button in the dialog doesn't work any more as well.
Maybe this is related to bug #157546, but I don't know, as the mount path is completely different.
Comment 4 Michael Gross 2006-03-15 15:17:51 UTC 
Packager problem, assigning to Jiri.
Comment 5 Marcel Hilzinger 2006-03-16 15:26:37 UTC 
Can reproduce with beta8 It´s the same problem as described in bug #157546.
My drive is a TOSHIBA DVD-ROM SD-M1612.
Comment 6 Marcel Hilzinger 2006-03-16 15:27:30 UTC 
So this isn`t a packager problem I guess...
Comment 7 Lukas Ocilka 2006-04-21 11:52:54 UTC 
According to comment #5 It seems to be a duplicate.

*** This bug has been marked as a duplicate of 157546 ***