Bug 95082

*** Bug 103878 has been marked as a duplicate of this bug. ***

Would it be possible to fix this bug before 10.0? Not having working grubonce
is a big problem for kernel development since I cannot test boot kernel unattended
anymore and there is no lilo to fall back to.

I'm currently busy working on 103031, but this one will be right after that. 

*** Bug 106037 has been marked as a duplicate of this bug. ***

*** Bug 113526 has been marked as a duplicate of this bug. ***

*** Bug 113627 has been marked as a duplicate of this bug. ***

Fixed in next release (-0.96-4 ?), by a complete rewrite.  

i assume this is syntax compatible to the 9.3 version and i do not need to
change anything in powersave?
Otherwise bug #103878 is not a duplicate of this one and will be reopened as
blocker :-)

Read the description: "grubonce doesn't work anymore". /usr/sbin/grubonce _is_ 
backward compatible with the previous version.  

The bug is still there in beta4. As this is the latest version we are 
betatesting right now, the bug cannot seriously be considered "FIXED". "FIXED" 
is a status, but the future by definition cannot have a status. Otherwise it 
would not be the future, would it? 

It will be fixed in RC1, the engineer has taken the appropriate action and
therefore the right to close this.

Btw. you will get RC1.

*** Bug 115160 has been marked as a duplicate of this bug. ***

unfortunately it still does not work in RC1 for me (it works on some systems, on
others it does not).

This is a totally different issue, likely a non obvious duplicate. 
And it's not a blocker any more. 

Ad #13: Please open another bug for this.

*** Bug 106037 has been marked as a duplicate of this bug. ***

So what do we now? I think this _is_ a blocker - if neither powersave nor kdm 
can reboot to a specific system, something that worked in 9.3 and has reported 
several times! 

The bug 106037 is still there with RC1, And because of the confusing messages 
here I seriously doubt that bug 106037 is really a duplicate of this one here. 
But I am supposed to reopen this one. So that's what I am doing. 

Will you at least sometimes trust the package maintainer?  
_This_ bug _is_ fixed.  
Bug #115910 has been reopened, just in case the real cause is not a duplicate.  
When I say "non obvious", I mean non obvious, meaning it may not be apparent  
to you on first sight.  
  
This bug was about the mechanism for grubonce having totally changed, and it  
required a complete re-implementation. I did that. Without it, grubonce would  
_never_ work. Now we have the problem that the new implementation _sometimes_  
fails, which is a different issue. (Bug #115910) 
  
Does this make it clear?  

One wonders why the grub people replaced a perfectly working patch
with one that has a totally different interface breaking scripts and "sometimes
fails"  That seems like several steps backwards.

During KDE shutdown one can choose which system should be rebooted (bug   
106037). But whatever I pick the full Grub menu comes up for reboot. This   
happens every time NOT sometimes. Plus everyone now is telling me it is a   
duplicate of this bug. So I trust the experts and I am telling you it is wrong   
to say the new implementation fails sometimes. It fails always on my systems.  
I strongly suggest to reopen this bug. Or shut down the beta test if you do  
not like the results of it.  

So, in the end it still does not work in 10.0 final. :-)

But I would not dare reopen this bug...