Bug 222547

Summary:	Installation of additional packages after installation fail when one is offline (even though DVD is present)
Product:	[openSUSE] openSUSE 10.2	Reporter:	Gerald Pfeifer <gp>
Component:	YaST2	Assignee:	Katarina Machalkova <kmachalkova>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	lslezak, ma
Version:	Beta 2 plus
Target Milestone:	---
Hardware:	i386
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2log-1 (the y2log file in question, I believe)

Description Gerald Pfeifer 2006-11-19 20:58:19 UTC

I installed 10.2 Beta2plus from scratch, and ticked off all installation sources
offered during installation.

Now I am offline (IMPORTANT: I believe this is key here) and when invoking YaST
"Software Management", it (correctly) complains that these installation sources
are not available, so I skip them in the respective error dialogs.

HOWEVER, once I am done with this and get into the "Software Management" screen,
it turns out that YaST also ignores the DVD I installed from, which still is in
my DVD drive.  No new patterns, packages,... can be added.

Only when I cancel the "Software Management" module, but not YaST, and
restart the "Software Management" module again, do I get the desired
behavior: now everyhing is in place, and the DVD is accessed and used properly.

How to repeat:

 1 Install system, enabling all options installation sources/channels
 2 Restart / put system online
 3 Invoke YaST
 4 Choose "Software Management"
 - There will be error messages on unavailable installation sources.  Skip each
   of these (by choosing "Skip").
 5 Try to search for a package not installed -- no match is presented!
 6 Exit "Software Management", but keep YaST running.
 7 Choose "Software Management" again.
 - No error messages.
 8 Try to search for a package not installed -- works just fine.

The bug materializes in step 5 (versus step 8)!

Comment 1 Jiří Suchomel 2006-11-21 09:42:51 UTC

Please attach the logfiles.
Ladislav, meabye some problem in source refresh?

Comment 2 Ladislav Slezák 2006-11-22 11:55:36 UTC

It looks strange, maybe a problem in libzypp?? The logs are really important...

Comment 3 Stefan Hundhammer 2006-11-28 10:34:56 UTC

No feedback - and the final deadline is coming nearer and nearer

Comment 4 Gerald Pfeifer 2006-11-28 14:16:00 UTC

Created attachment 107198 [details]
y2log-1 (the y2log file in question, I believe)

Sorry took me some time to dig out the logs.

As far as I can remember (close to 100% confidence,
the issue happend on the 17th around 6pm.

Comment 5 Stefan Hundhammer 2006-11-28 14:42:26 UTC

I don't know: y2-packager or libzypp.

Comment 6 Michael Andres 2006-11-28 23:54:28 UTC

Quite hard do see something in the log. But this again reveals the 'special' behaviour of the ncurses UI. On the contrary to qt, ncurses contoll center does not launch a new process for each request.

This becomes manifest in step 4 vs. step 7. The 1st run reports errors while launching the sources. Susequent calls don't, as sources are already up. This leads to different, apparently inconsistent behaviour.

AFAIK YaSTs ycp code is not prepared to cope with these different situations. Same as the user, ycp code tends to expect a fresh libzypp, and does not expect it to be reused afterwards. 

The IMO neccessary fix would be to fix ncurses to behave like qt. That way each lauch of "Software Management" (and others) will show the same behaviour.

Comment 8 Katarina Machalkova 2006-11-29 13:23:57 UTC

Gerald, just to be 100% sure - does this happen only if you invoke Software management from ncurses menu (and not in Qt menu or not by running new 'yast sw_single' from commandline each time)?

Comment 9 Gerald Pfeifer 2006-11-29 23:24:37 UTC

I haven't thought of testing these two other cases back then, sorry.
(If this occurs again, I will try to remember and test also these options.)

Comment 10 Katarina Machalkova 2006-12-06 16:57:11 UTC

I've just fixed yast ncurses menu to launch the modules as separate processes, but I'm not sure if it will fix this issue (package management is not exactly my cup of tea ;-) )
The fixed packages are yast2-2.15.0, yast2-ncurses-2.15.1 and yast2-core-2.15.1. Please try with those (once they come out of autobuild). If the problem persists, it needs to be reopened and assigned to lslezak or to zypp folks