http://bugzilla.novell.com/show_bug.cgi?id=555323 Vadim Krevs changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|vkrevs@yahoo.com | --- Comment #2 from Vadim Krevs 2009-11-16 11:43:09 UTC --- Created an attachment (id=327683) Required y2logs attached -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323#c shuang qiu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |duwe@novell.com AssignedTo|bnc-team-screening@forge.pr |jkupec@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c5 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |vkrevs@yahoo.com --- Comment #5 from Josef Reidinger 2009-11-30 12:34:53 UTC --- It looks like adding bootloader is not invoked at all. How exactly you update? via zypper dup? or something different? I need this info to reproduce it. Especially if yast run during your update. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c7 --- Comment #7 from Ján Kupec 2009-11-30 13:48:16 UTC --- Did you execute SuSEconfig after the 'dup'? (it's needed when YAST_IS_RUNNING=instsys is used) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c8 --- Comment #8 from Josef Reidinger 2009-11-30 13:49:47 UTC --- Yeah, that is root of problems. if you specify YAST_IS_RUNNING=instsys then perl-Bootloader is in another mode and don't write changes immediately, but to specified file and which must be then runned. Really not good idea to speicify it on running system which need to update bootloader configuration. I add it to that wiki page. So bug is invalid, as when you simulate instsys then behavior is changes and menu.lst is not updated (because you cannot modify menu in instsys, but on target machine). Jano - I think it doesn't help in this case as pbl need more variables defined by yast2-bootloader and afterwards yast2-bootloader run pbl delayed update. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c10 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #10 from Josef Reidinger 2009-12-01 15:37:45 UTC --- OK, closed as invalid and add to wiki big warning, as simulating inst-sys cause serious problem to update bootloader. Thanks for report -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c12 --- Comment #12 from Josef Reidinger 2009-12-01 16:05:25 UTC --- (In reply to comment #11)

Josef, what about using YAST_IS_RUNNING=1 ? Does that make a difference?

Yes, perl-Bootloader checks only instsys value... and Überhack is if you use DELAYED_RUN_UPDATE_BOOTLOADER=yes Then perl-Bootloader think that he run delayed update. But as I said it is hack and internal implementation which should not be official way. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c14 --- Comment #14 from Josef Reidinger 2009-12-01 16:41:34 UTC --- (In reply to comment #13)

Sorry for a silly question, but how is one supposed to perform a distribution upgrade using zypper dup if bootloader config is not updated? Isn't that a showstopper? Or am I missing something here?

of course zypper dup works. what doesn't work is if you run YAST_IS_RUNNING=instsys zypper dup because it simulate upgrade from instsys and not on running system -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555323 http://bugzilla.novell.com/show_bug.cgi?id=555323#c16 --- Comment #16 from Ján Kupec 2010-01-06 12:41:45 UTC --- Well, many people (most) do not have to switch to runlevel 3, they can successfully run zypper dup while using the graphics environment. So, yes, we can recommend to switch to runlevel 3, but only as a workaround to the crashing X problem. OTOH, we can probably change the suggestion in the wiki to YAST_IS_RUNNING=1 instead of YAST_IS_RUNNING=instsys (if that works around the crashing X problem). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.