Bug 393898 - System configuration skip
Summary: System configuration skip
Status: RESOLVED DUPLICATE of bug 393143
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 3
Hardware: x86-64 openSUSE 11.0
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michael Meeks
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-23 10:04 UTC by Mircea Bujanca
Modified: 2008-05-30 20:59 UTC (History)
1 user (show)

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


Attachments
Yast2 log files (1.24 MB, application/x-gzip)
2008-05-30 11:29 UTC, Mircea Bujanca
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mircea Bujanca 2008-05-23 10:04:15 UTC
openSuSE 11.0 Beta 3 x86_64   (DVD)
Graphical mode
English
After instlation of the packeges, at the end, on system configuration:
Apears the message with detecting DSL card, I disabled the firewall, ipv6, tryed to configure my network cards: Seted my static IP, netmask, Hostname, before to configure all my settings and hit finish, after some time, the install just exit from menu and booting ahead, nothing from my choises were saved. After reboot, the install menu on this stage apears again to set system configuration, repeats the process, detect DSL card ..... after some time it skips my preferences and boot ahead; the next time when I rebooted, when the menu from install apears again I just hit finish and in this way saved the default config and boot normaly on Gnome. 
I configured my network card from Yast, and now it's been saved.

Thx.
Comment 1 Andreas Jaeger 2008-05-23 10:49:35 UTC
Please attach the YaST log files (as explained under http://en.opensuse.org/Bugs/YaST)
Comment 2 Mircea Bujanca 2008-05-30 11:29:14 UTC
Created attachment 219127 [details]
Yast2 log files

I have attached the log files.


Thanks,
Comment 3 Michael Andres 2008-05-30 13:31:25 UTC
2008-05-22 14:32:25 <3> mircea(3352) [liby2] genericfrontend.cc(log_backtrace):97 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
   Frame  3: /usr/lib64/libgdk-x11-2.0.so.0
   Frame  4: /usr/lib64/libgdk-x11-2.0.so.0(gdk_window_set_cursor+0xa1) 
   Frame  5: /usr/lib64/YaST2/plugin/libpy2gtk.so.2
   Frame  6: /usr/lib64/libgtk-x11-2.0.so.0
   Frame  7: /usr/lib64/libgobject-2.0.so.0(g_closure_invoke+0x16d) 
   Frame  8: /usr/lib64/libgobject-2.0.so.0
   Frame  9: /usr/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0x672) 
   Frame 10: /usr/lib64/libgobject-2.0.so.0(g_signal_emit+0x83) [0x7f4e3e378a53]
   Frame 11: /usr/lib64/libgtk-x11-2.0.so.0
   Frame 12: /usr/lib64/libgtk-x11-2.0.so.0(gtk_propagate_event+0xe3) 
   Frame 13: /usr/lib64/libgtk-x11-2.0.so.0(gtk_main_do_event+0x2eb) 
   Frame 14: /usr/lib64/libgdk-x11-2.0.so.0
   Frame 15: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x24a) 
   Frame 16: /usr/lib64/libglib-2.0.so.0
   Frame 17: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x6c) 
   Frame 18: /usr/lib64/YaST2/plugin/libpy2gtk.so.2  YGUI::waitInput(unsigned long, bool)
   Frame 19: /usr/lib64/libyui.so.3  YDialog::waitForEvent(int)
   Frame 20: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YCP_UI::doUserInput(char const*, long, bool, bool)
   Frame 21: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YCP_UI::UserInput()
   Frame 22: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YUINamespace::UserInput()
   Frame 23: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YUIFunction::evaluateCall_int()
   Frame 24: /usr/lib64/YaST2/plugin/libpy2UI.so.2  YCPBuiltinCaller::call()
   Frame 25: /usr/lib64/libyui.so.3  YUI::uiThreadMainLoop()
   Frame 26: /usr/lib64/libyui.so.3  start_ui_thread(void*)
   Frame 27: /lib64/libpthread.so.0 


Looks like 'installation ("continue") gtk' crashes. That's why it is started over and over.
 
Comment 4 Forgotten User h13THG8RK1 2008-05-30 20:59:09 UTC

*** This bug has been marked as a duplicate of bug 393143 ***