|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast Software management doesn't start after last zypper / libzypp update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Sharon Malevsky <s.malevsky> |
| Component: | YaST2 | Assignee: | Forgotten User h13THG8RK1 <forgotten_h13THG8RK1> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | forgotten_h13THG8RK1, lmedinas, ma, meissner, sshaw |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | My yast log | ||
|
Description
Sharon Malevsky
2009-05-13 12:26:16 UTC
does: zypper up report any errors? could you can also attach YAST2 Logfiles? I can reproduce this bug too, i'm not sure if it was zypper update but it sounds like it. Heres the log: 2009-05-20 19:21:32 <2> fermi(13997) [YCP] clients/inst_packages.ycp:50 Warning: inst_packages.ycp client is obsoleted, use module PackagesUI.ycp instead 2009-05-20 19:21:32 <1> fermi(13997) [YCP] clients/inst_packages.ycp:51 Stage: normal, Mode: normal, Args: [$ ["dialog_type":`searchMode, "repo_mgmt":true]] 2009-05-20 19:21:32 <1> fermi(13997) [YCP] clients/inst_packages.ycp:62 inst_packages called with options: [$ ["dialog_type":`searchMode, "repo_mgmt":true]] 2009-05-20 19:21:32 <1> fermi(13997) [YCP] PackagesUI.ycp:193 Called RunPackageSelector($["display_support_st atus":nil, "enable_repo_mgr":true, "mode":`searchMode]) 2009-05-20 19:21:32 <1> fermi(13997) [YCP] PackagesUI.ycp:174 Feature display_support_status: false 2009-05-20 19:21:32 <1> fermi(13997) [YCP] PackagesUI.ycp:211 Running package selection, mode: `searchMode, o ptions: display repo management: true, display support status: false 2009-05-20 19:21:32 <1> fermi(13997) [YCP] PackagesUI.ycp:230 Options for the package selector widget: `opt ( `searchMode, `repoMgr) 2009-05-20 19:21:32 <1> fermi(13997) [ui-pkg] YPackageSelector.cc(YPackageSelector):30 YPackageSelector flags : 48 2009-05-20 19:21:33 <3> fermi(13997) [liby2] genericfrontend.cc(signal_handler):196 got signal 11 at YCP file PackagesUI.ycp:232 2009-05-20 19:21:33 <3> fermi(13997) [liby2] genericfrontend.cc(log_stored_debug):120 Liberating suppressed d ebugging messages: 2009-05-20 19:21:33 <3> fermi(13997) [liby2] genericfrontend.cc(log_stored_debug):122 End of suppressed debug ging messages 2009-05-20 19:21:33 <3> fermi(13997) [liby2] genericfrontend.cc(log_backtrace):144 Back trace: Frame 0: /usr/lib64/liby2.so.2 log_backtrace() Frame 1: /usr/lib64/liby2.so.2 signal_handler(int) Frame 2: /lib64/libc.so.6 [0x7fbe826e16e0] Frame 3: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Ypp::Node::child() Frame 4: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Ypp::Impl::polishCategories(Ypp::Package::Type) Frame 5: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Ypp::Impl::getPackages(Ypp::Package::Type) Frame 6: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Ypp::getFirstCategory2(Ypp::Package::Type) Frame 7: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Collections::Categories::doBuild(_GtkTreeStore*) Frame 8: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Collections::StoreView::build(bool, bool, bool, bool) Frame 9: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 Collections::setType(Collections::Type, bool, bool) Frame 10: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 PackageSelector::PackageSelector(_YGtkWizard*, bool, boo l, bool) Frame 11: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 YGPackageSelector::YGPackageSelector(YWidget*, long) Frame 12: /usr/lib64/YaST2/plugin/libpy2gtk.so.2 YGWidgetFactory::createPackageSelector(YWidget*, long) Frame 13: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YCPDialogParser::parsePackageSelector(YWidget*, YWidgetOp t&, YCPTerm const&, YCPList const&, int) Frame 14: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YCPDialogParser::parseWidgetTreeTerm(YWidget*, YWidgetOpt &, YCPTerm const&) Frame 15: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YCPDialogParser::parseWidgetTreeTerm(YWidget*, YCPTerm co nst&) Frame 16: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YCP_UI::OpenDialog(YCPTerm const&, YCPTerm const&) Frame 17: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YUINamespace::OpenDialog(YCPTerm const&, YCPTerm const&) Frame 18: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YUIFunction::evaluateCall_int() Frame 19: /usr/lib64/YaST2/plugin/libpy2UI.so.2 YCPBuiltinCaller::call() Frame 20: /usr/lib64/libyui.so.3 YUI::uiThreadMainLoop() Frame 21: /usr/lib64/libyui.so.3 start_ui_thread(void*) Frame 22: /lib64/libpthread.so.0 [0x7fbe84158070] Frame 23: /lib64/libc.so.6(clone+0x6d) [0x7fbe8278210d] == End of back trace === Looks like a gtk ui problem. Looks like a hijacked bug, too :O) Sharon, if you can get us your yast logs, we can tell, whether your problem is the same as Luis'. Created attachment 293938 [details]
My yast log
I don't think this is related to GTK UI since there wasn't any update for YAST-GTK. Only for zypper/libzypp. Ok found the problem, move back to libzypp-5.25.3-0.1.2.x86_64 solved my problem. Now i can start Yast software management. Luis, yes, libzypp must have changed some API behavior... The gtk UI crash was absolutely unnecessary though and we must inquire that before all. Anyway, looks like another reporter got ahead of you: ;) *** This bug has been marked as a duplicate of bug 504424 *** |