Bug 493997 - all YaST2-gtk modules crash
Summary: all YaST2-gtk modules crash
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Factory
Hardware: x86-64 Other
: P3 - Medium : Major with 5 votes (vote)
Target Milestone: ---
Assignee: Martin Kudlvasr
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-10 16:26 UTC by Jan Matejek
Modified: 2009-04-30 10:01 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast2 logs (2.47 MB, application/x-bzip2)
2009-04-10 16:29 UTC, Jan Matejek 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Matejek 2009-04-10 16:26:12 UTC 
steps to reproduce:

1. install latest Factory

2. launch any yast2 module in a way that makes it use GTK UI

3. observe a crash:

YaST got signal 11 at YCP file Wizard.ycp:342
/sbin/yast2: line 437:  9196 Segmentation fault (SIGSEGV)                     $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

yast2 log says this:

2009-04-10 18:24:18 <1> ws-pool1(9498) [ui] YUI.cc(YUI):62 Creating UI with threads
2009-04-10 18:24:18 <3> ws-pool1(9498) [liby2] genericfrontend.cc(signal_handler):216 got signal 11 at YCP file Wizard.ycp:342
2009-04-10 18:24:18 <3> ws-pool1(9498) [liby2] genericfrontend.cc(log_stored_debug):140 Liberating suppressed debugging messages:
2009-04-10 18:24:18 <3> ws-pool1(9498) [liby2] genericfrontend.cc(log_stored_debug):142 End of suppressed debugging messages
2009-04-10 18:24:18 <3> ws-pool1(9498) [liby2] genericfrontend.cc(log_backtrace):164 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 [0x7f71816956e0]
   Frame  3: /usr/lib64/YaST2/plugin/libpy2gtk.so.2  YGApplication::makeScreenShot(std::string)
   Frame  4: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YCP_UI::OpenDialog(YCPTerm const&, YCPTerm const&)
   Frame  5: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YUINamespace::OpenDialog(YCPTerm const&, YCPTerm const&)
   Frame  6: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YUIFunction::evaluateCall_int()
   Frame  7: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YCPBuiltinCaller::call()
   Frame  8: /usr/lib64/libyui.so.3  YUI::uiThreadMainLoop()
   Frame  9: /usr/lib64/libyui.so.3  start_ui_thread(void*)
   Frame 10: /lib64/libpthread.so.0 [0x7f718310e070]
   Frame 11: /lib64/libc.so.6(clone+0x6d) [0x7f718173610d]

== End of back trace ===
Comment 1 Jan Matejek 2009-04-10 16:29:49 UTC 
Created attachment 285217 [details]
yast2 logs

attaching complete y2logs

this happens only with gtk interface, qt and curses work fine
Comment 2 Martin Kudlvasr 2009-04-29 11:18:41 UTC 
I tested current yast trunk (on sled11) and modules work ok. I'll try the factory ...
Comment 3 Martin Kudlvasr 2009-04-29 14:10:36 UTC 
I just tried build66, x86_64 and detected no problems. Please test if the problem persist on your machine in os11.2-milestone1. 
Lowering the severity as this is an invalid candidate ...
Comment 4 Jan Matejek 2009-04-30 10:01:45 UTC 
yup, can't reproduce with today's factory either.
-> closing as fixed