Bug 138225

Please, attach y2log (see http://www.opensuse.org/Bug_Reporting_FAQ#YaST)

Created attachment 60400 [details]
y2log

The needed information has been attached.

Jirka, here you go. Do not get confused by the printer log at the bottom of the log, it's from a different process. Look for 2005-12-13 10:16:54.

I cannot see anything pointing to the users in the log; did it fall during inst_auth? But there is no milestone log before it would exit... 
Couldn't the problem be in the NetworkDevices::List("") call?

Yes, the moment I clicked the "next" button for proceeding to the users management step, it went off.

Here I see that inst_auth is the last thing running in PID 3601. I don't know which List call you mean (timestamp?).

2005-12-13 10:16:54 <1> linux(3601) [Interpreter] ProductControl.ycp:179 Calling YaST client inst_auth (arguments: [$["enable_back":true, "enable_next":true]])
2005-12-13 10:16:54 <1> linux(3601) [wfm] Y2WFMComponent.cc(import):695 Y2WFMComponent::import (PackageCallbacks)
...
2005-12-13 10:16:54 <1> linux(3601) [wfm] Y2WFMComponent.cc(import):695 Y2WFMComponent::import (PackageCallbacks)
2005-12-13 10:16:54 <1> linux(3601) [packagemanager] InstSrcManager.cc(enableDefaultSources):995 Going to enable all default InstSrc'es...
2005-12-13 10:16:54 <1> linux(3601) [packagemanager] InstSrcManager.cc(enableDefaultSources):995 Going to enable all default InstSrc'es...
2005-12-13 10:18:46 <1> linux(9444) [liby2] genericfrontend.cc(main):193 Launched YaST2 component 'y2base'

I mean NetworkDevices::List("") call from inst_auth.

It is the first function call in inst_auth.ycp, that's why I thought there might be the problem.

It the described behaviour reproducible?
If so, please use Shift-F7 (=verbose logging: http://www.opensuse.org/Bug_Reporting_FAQ#YaST) before you exit network configuration, than continue and attach new y2logs.

Do I have to reinstall SuSE, or I can just try to reconfigure network conncetions?

It should be possible to start just the second stage of the installation (- that's the one begining with the root password dialog; whole stage will acctualy contain only configuration parts, not the installation).

touch the file /var/lib/YaST2/runme_at_boot and restart

There's no such file, but I've found /var/lib/YaST2/step, that contains:
continue_12

Shall I change it?

No, sorry for no explanation. Touch the file = create the file (just call "touch  /var/lib/YaST2/runme_at_boot").
The presence of the file means that the second stage of installation should start after reboot, so it surely cannot exist now (it is deleted after the installatiuon).

Something strange happened. First time I tried Shift-F7 (before proceeding to the user management), the logging dialog showed up and it made the installation freeze and I had no choice but rebooting.
Then I tried again and pressed Shift-F7 before setting the root management, set it to log the setup, then continued and everything went fine. The only difference is that I used shorter root password.

What would you like me to do?

Hm... I don't know.

Anyway, this is not yast2-users related. Stano?

Michael, the crash seems to be in package manager. Anything you could read out of logs?

Are you shure? I see no hint, that it's actually the packagemanager.

The last loglines "InstSrcManager.cc(enableDefaultSources)" originate from a call to 'Pkg::sourceStartManager(true)'. If you look at y2logs, you'll notice that this is called quite often. And the call did not perform any real action. If there were sources to enable/disble, the perceeding call would have done it. And if anything had changed between the two calls, there would have been a logline.

I guess controll is back in YCP.

The last ycp client that was called was inst_auth.ycp (as seen in comment #6); this client calls Package::Available ("yast2-nis-client"). PackageSystem::Available calls only
  EnsureSourceInit();
  return Pkg::IsAvailable(package);

Jiri, please check, if all needed packages for the users management are installed.

According to y2logRPM, yes (all packages in Require list of yast2-users).

(But the packages checked for "Available" as written in comment #17 don't have to be installed)

Was there any error report on the console when YaST quit?

I'm not sure, so I'll recheck when Beta 1 is released.

No response. Please reopen if happens again.