Bug 238556

Summary:	YaST2 not Installing programs
Product:	[openSUSE] openSUSE 10.2	Reporter:	Adam Jimerson <vendion>
Component:	YaST2	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs 0-3

Description Adam Jimerson 2007-01-25 02:09:05 UTC

For some unknown reason I do not have a "Install with YaST" option in my right click menu, so I have to go in though KRPMView and use the "Install with YaST" Button from there.  At first it seems to work it will as for the root password, then it will go anywhere around thirty minutes without doing anything.  Sometimes the process seems to disappear from the process list without notifying of this.  To fix this some times re clicking the "Install with YaST" button and re input my root password before YaST will pop up and start the process.  What happens next depends on if the install request was stopped or not.  Very rarely does it really install the program.  I would use ZENworks to install the program, last version of SUSE had no problem using it, but the only thing I can get ZENworks to due is to update programs.

Comment 1 Cyril Hrubis 2007-01-25 15:00:27 UTC

Please attach y2logs. If you are in doubt please follow:

http://en.opensuse.org/Bugs/YaST


Thanks!

Comment 2 Adam Jimerson 2007-01-27 02:24:21 UTC

Created attachment 115625 [details]
y2logs 0-3

Here is the y2logs 0-3, I hope this is all that you need for now, because I really need to install the pre version PowerSave

Comment 3 Ladislav Slezák 2007-01-29 06:44:49 UTC

According to the log there is another process accessing the package manager library (libzypp):

2007-01-26 20:57:35 <1> SE-02(5173) [zypp] ZYppFactory.cc(zyppLocked):212 4584 is running and has a ZYpp lock. Sorry           

Make sure that there is no other yast module running or another process accessing the package manager.

The yast module which install the package should inform user better...

Comment 4 Ladislav Slezák 2007-01-29 07:34:31 UTC

I think that problem is in constructor in Product.ycp, according the log there are two Pkg calls which do not check whether the package manager is accessible:

2007-01-26 20:57:29 <1> SE-02(5173) [wfm] Product.ycp:140 Pkg Builtin called: TargetInitialize                                 
2007-01-26 20:57:41 <1> SE-02(5173) [wfm] Product.ycp:75 Pkg Builtin called: TargetProducts                                    

And after that Pkg::Connect is finally called which checks the accessibillity and shows the error dialog:

2007-01-26 20:57:53 <1> SE-02(5173) [wfm] PackageLock.ycp:30 Pkg Builtin called: Connect                                       

The two extra calls cause long timeout and the user is confused and starts the module again which cannot get the lock again...

The constructor must be fixed - it should use PackageLock::Check() and do not call any Pkg:: function if the package manager is not accessible.

(Adam, the problem with missing "Install" menu is another problem, it should be reported separately and assigned to KDE component. Thanks!)

Comment 5 Adam Jimerson 2007-01-29 21:20:12 UTC

How would correcting this problem come about? 

(Yea, I was going to get this problem taken care of first, because this problem right now is more important than being able to install an RPM from the context menu.)

Comment 6 Lukas Ocilka 2007-01-31 13:45:02 UTC

- Calling PackageLock::Check before Pkg calls (#238556).

Fixed in yast2-installation-2.13.181

Comment 7 Adam Jimerson 2007-01-31 20:31:00 UTC

How would I get this fix?

Comment 8 Lukas Ocilka 2007-02-01 09:18:51 UTC

If you need this fix, download the last yast2-installation from FACTORY, however you will need yast2-installation-2.15.6 (which will be there in 2 or 3 days I guess).

The problem is ZENworks, if you disable zmd daemon (rczmd stop), you can install programs whenever you want. ZENworks probably locks the packager. You can't run two programs at which would access the RPM database at once.

I don't know much about "Install with YaST" but you can always run 'yast2 sw_single' or YaST -> Software -> Software Management and install packages that way. My patch of the yast2-installation can't solve ZMD blocking packager.