Bug 129511

Summary: cloning grub boot loader item in Yast causes cloned item to be renamed
Product: [openSUSE] SUSE LINUX 10.0 Reporter: J.B. Gill <jbgill>
Component: YaST2Assignee: Jiri Srain <jsrain>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: RC 4   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast logs

Description J.B. Gill 2005-10-19 20:11:48 UTC 
Configuration: SUSE Linux 10.0 with grub boot loader installed.

Steps to reproduce:
1. go into Yast Control Center, then System, then Boot Loader
2. highlight an item to be cloned, then click "Add" button
3. Choose "Clone Selected Section" and click "Next"
4. type in a new section name and click "OK"
5. Take note of the section list - All is OK at this point
6. Click "Finish" to commit changes and exit
7. Go back into "Boot Loader" tool
8. Notice that the list is now wrong.  There are now two items with the same
name - the old item we made a clone of has been renamed to the name of the new item.
Comment 1 Jiri Srain 2005-10-21 08:56:45 UTC 
I cannot reproduce the bug, please, attach the YaST logs (see

http://www.opensuse.org/Bug_Reporting_FAQ#YaST

for info how to attach the logs)
Comment 2 J.B. Gill 2005-10-24 14:56:42 UTC 
Created attachment 55219 [details]
yast logs
Comment 3 J.B. Gill 2005-10-24 15:02:17 UTC 
It is easily reproduced on my box.  I have attached YaST logs.  If you need anything else, let me know.  I can give you remote access to the box if needed.
Comment 4 Michael Gross 2005-10-25 12:24:43 UTC 
I could not reproduce this either.
Jiri: Please decide what should be done.
Comment 5 Jiri Srain 2005-10-26 11:26:28 UTC 
Ah, reproduced it. The trick is not to clone the 1st section (it works due to another bug)
Comment 6 Jiri Srain 2005-10-26 11:30:06 UTC 
Andreas, please, consider putting a patched version to FTP (even if it is not critical and this is the only report so far). The fix is a one-liner. I may also fix it in SVN and release the fix if more problems occurre.

Fixed in SVN for 10.1 for now.
Comment 7 Andreas Jaeger 2005-10-26 14:02:05 UTC 
Please fix it in SVN for 10.0, if further bugs come, we will do one consolidated update.  for now let's not do a YOU update.
Comment 8 Jiri Srain 2005-10-31 10:03:50 UTC 
OK, done.