[opensuse-factory] Serious problem with Tumbleweed upgrade to 12.2
Hi, There is something seriously wrong with upgrade of Tumbleweed to 12.2 My Tumbleweed based on 12.1 was up to date day before 12.2 was announced. Yesterday I run actualization and now I'm not able to run X sever. First I thought that there was some bug in new version of X server related to my video card, but today my cousin with completely different hardware informed me about the same problem. I also googled out similar problems in opensuse forums e.g.: http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/477936... http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/477823... http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/477943... Do you know about this problem and maybe identified the sources of it? Is there any way to recover to usable system other than installation of 12.2 from ground up? I will provide any additional information needed to solve this bug. I would appreciate any hint. thank you in advance Andrzej -- Poczta wyslana z portalu Panorama Internetu sp. z.o.o -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Sep 10, 2012 at 06:17:22PM +0200, superandrzej@epf.pl wrote:
It seems that people aren't doing: zypper dup to update for 12.2. Did you try that? On one of my boxes, X died half way through, and I had to continue with the update from a console. The other one, it worked just fine, no problems at all. I have had reports of it working fine for some people, and like you, others report problems of X dieing. But that should be recoverable with 'zypper dup', right? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg,
Reading http://en.opensuse.org/Portal:Tumbleweed gave me an impression that "zypper dup" is needed only when you enable Tumbleweed for the first time. Maybe it can be mentioned on that page that everytime new "base" system is released "zypper dup" should be run and not Apper or YaST.
but.... after reboot the system was not booting. It turned out that GRUB was configured for the "old" tumbleweed kernel 3.5.3-40 that was replaced by 3.4.6-2.10 when "zypper dup" was run. After manually editing GRUB options I was able to boot. Now I'm reinstalling all packages to make sure no package is broken. Thank you Greg very much for the advice. Andrzej -- Poczta wyslana z portalu Panorama Internetu sp. z.o.o -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Sep 12, 2012 at 11:58:42PM +0200, Andrzej Szelachowski wrote:
No, you should ALWAYS use 'zypper dup' for normal Tumbleweed operation, otherwise it will break. I keep trying to get this across more, any help in this is appreciated. Glad you got things working again. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Sep 10, 2012 at 06:17:22PM +0200, superandrzej@epf.pl wrote:
It seems that people aren't doing: zypper dup to update for 12.2. Did you try that? On one of my boxes, X died half way through, and I had to continue with the update from a console. The other one, it worked just fine, no problems at all. I have had reports of it working fine for some people, and like you, others report problems of X dieing. But that should be recoverable with 'zypper dup', right? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Greg,
Reading http://en.opensuse.org/Portal:Tumbleweed gave me an impression that "zypper dup" is needed only when you enable Tumbleweed for the first time. Maybe it can be mentioned on that page that everytime new "base" system is released "zypper dup" should be run and not Apper or YaST.
but.... after reboot the system was not booting. It turned out that GRUB was configured for the "old" tumbleweed kernel 3.5.3-40 that was replaced by 3.4.6-2.10 when "zypper dup" was run. After manually editing GRUB options I was able to boot. Now I'm reinstalling all packages to make sure no package is broken. Thank you Greg very much for the advice. Andrzej -- Poczta wyslana z portalu Panorama Internetu sp. z.o.o -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Sep 12, 2012 at 11:58:42PM +0200, Andrzej Szelachowski wrote:
No, you should ALWAYS use 'zypper dup' for normal Tumbleweed operation, otherwise it will break. I keep trying to get this across more, any help in this is appreciated. Glad you got things working again. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Andrzej Szelachowski -
Greg KH -
superandrzej＠epf.pl