The last time I updated, Yast2 got hosed. Error: terminate called after throwing an instance of 'TUIUnsupportedWidgetException' what(): Unsupported optional widget type: ContextMenu YaST got signal 6 at YCP file Wizard.ycp:688 /sbin/yast2: line 421: 25381 Aborted ....................... How do I fix this ? -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing & Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home & Business user of Linux - 10 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Duaine & Laura Hechler wrote:
The last time I updated, Yast2 got hosed.
Error: terminate called after throwing an instance of 'TUIUnsupportedWidgetException' what(): Unsupported optional widget type: ContextMenu YaST got signal 6 at YCP file Wizard.ycp:688 /sbin/yast2: line 421: 25381 Aborted .......................
How do I fix this ?
Well, I don't know... However, the combined wisdom at backing out bad updates that have hosed things seems to be: First check to see if the ncurses (text) version of yast will still work, and also check zypper so you know if you are dealing with (1) a yast gui problems (2) a total yast failure, and/or (3) a zypper failure. If you still have zypper and not yast, then using zypper from the command line will save you the work of manually downloading rpms to install and you can use zypper with your DVD to downgrade any recent yast updates. Let us know what still works. Next (From Carlos) rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{PACKAGER}\n" | sort | cut --fields="2-" | less -S Which basically queries the rpm database for the most recently installed updates and patches and gives you a list (output into less) that you can review to see if you can identify and yast/zypper related updates potentially causing the problem. Then if from that you get several rpms that are yast related, go download the corresponding original rpms from the oss repository (or your DVD) and downgrade back to the original version using 'rpm -Uvh --oldpackage (your list of rpms)' Before going further, post back and let us know what pieces still work and what you found from the rpm -q -a --queryformat command which should add more information. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
Duaine & Laura Hechler wrote:
The last time I updated, Yast2 got hosed.
Error: terminate called after throwing an instance of 'TUIUnsupportedWidgetException' what(): Unsupported optional widget type: ContextMenu YaST got signal 6 at YCP file Wizard.ycp:688 /sbin/yast2: line 421: 25381 Aborted .......................
How do I fix this ?
Well,
I don't know... However, the combined wisdom at backing out bad updates that have hosed things seems to be:
First check to see if the ncurses (text) version of yast will still work, and also check zypper so you know if you are dealing with (1) a yast gui problems (2) a total yast failure, and/or (3) a zypper failure. If you still have zypper and not yast, then using zypper from the command line will save you the work of manually downloading rpms to install and you can use zypper with your DVD to downgrade any recent yast updates. Let us know what still works.
Next (From Carlos)
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{PACKAGER}\n" | sort | cut --fields="2-" | less -S
Which basically queries the rpm database for the most recently installed updates and patches and gives you a list (output into less) that you can review to see if you can identify and yast/zypper related updates potentially causing the problem. Then if from that you get several rpms that are yast related, go download the corresponding original rpms from the oss repository (or your DVD) and downgrade back to the original version using 'rpm -Uvh --oldpackage (your list of rpms)'
Before going further, post back and let us know what pieces still work and what you found from the rpm -q -a --queryformat command which should add more information.
Somehow I got a mixture of 2.16 and 2.18. I did rpm -Uvh --force --oldpackage yast2* and that fixed it Thanks, Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ Tuning, Servicing & Rebuilding Reed Organ Society Member Florissant, MO 63034 (314) 838-5587 dahechler@att.net www.hechlerpianoandorgan.com -- Home & Business user of Linux - 10 years -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Duaine & Laura Hechler wrote:
Somehow I got a mixture of 2.16 and 2.18.
I did
rpm -Uvh --force --oldpackage yast2*
and that fixed it
Thanks, Duaine
Great, glad you got it fixed. Nothing worse than a broken yast. Just FYI, no need to use both --force and --oldpackage. While --force implies --oldpackage, the same isn't true. The general consensus for downgrading rpms is to just use --oldpackage. That way you haven't completely thrown away all protections that rpm provides against doing something terrible to yourself.... (not that I'm one to talk, --force was my downgrade option until it was pointed out that wasn't the best way to go about it;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
David C. Rankin
-
Duaine & Laura Hechler