Bug 854560

Hi, would you please attach the yast logs, see here: http://en.opensuse.org/openSUSE:Bugreport_YaST

Created attachment 572378 [details]
logs of yast as requested

Normally one should (I have read this now) do this right after the event. Sorry, I did not know. The event was the same day that I did report the bug or shortly before (I do not recall precisely). Hope that helps somehow. Attachment is there.

Could be a problem with libyui-qt-pkg or libzypp.

If it was libzypp, zypper should suffer the same problem, but I never heard about something like this.

This happened again as before. It might be that this is connected with updates from the packman repo? (yesterday I did one of 42 new updates, then when checking this morning all packages where set to "installable", no taboos set and about 20 packages to be installed (especially the by me tabooed avahi, samba and all remote admin packages...). 
This was all done with yast in gui, not zypper, not apper which is running, but was not used for update, just as "sentinel" for new fixes.

  grep 'Calling SAT Solver\|setLocks.*Lock.*item.*avahi\|Starting solving....' 

@Thomas: I checked every call to the resolver within the provided logs. There is no indication for a libzypp error. Locks are read, applied and always visible to the resolver. There is e.g. not a single solver run without avahi being in locked state.

I saw several YUI errors. Don't know if this is related:
 2013-12-12 16:48:59 <3> linux-lw5x.site(5276) [ui] YUIPlugin.cc(YUIPlugin):50 
  Could not load UI plugin "qt_zypp_solver_dialog": 
   libyui-qt_zypp_solver_dialog.so.5: 
    impossibile aprire il file oggetto condiviso: 
     File o directory non esistente
 2013-12-12 16:48:59 <3> linux-lw5x.site(5276) 
  [qt-ui] YQZyppSolverDialogPluginStub.cc(YQZyppSolverDialogPluginStub):69
   Plugin qt_zypp_solver_dialog does not provide ZYPPP symbol

would it be helpfull the next time that this comes up, to just let the install go as forseen by yast and send you the yast-logfiles? (I can restore the desired status anyway afterwards). You just tell me if it would help you to pin down the issue and I will.

(In reply to comment #6)
> I saw several YUI errors. Don't know if this is related:
>  2013-12-12 16:48:59 <3> linux-lw5x.site(5276) [ui] YUIPlugin.cc(YUIPlugin):50 
>   Could not load UI plugin "qt_zypp_solver_dialog": 
>    libyui-qt_zypp_solver_dialog.so.5: 
>     impossibile aprire il file oggetto condiviso: 
>      File o directory non esistente
>  2013-12-12 16:48:59 <3> linux-lw5x.site(5276) 
>   [qt-ui] YQZyppSolverDialogPluginStub.cc(YQZyppSolverDialogPluginStub):69
>    Plugin qt_zypp_solver_dialog does not provide ZYPPP symbol

This error means that package libqdialogsolver1 is not installed on the system. This plug-in's purpose is to visualize package dependencies. Thus, the error messages above are not related to this bug.

FYI: I reported the Bug 859195 today. In relation to this: there have been packman updates today and the kde update 4.11.4 yesterday. After the KDE one the situation seemed to be still normal. I installed the packman ones with apper this morning and then (probably not correlated) encountered the bug as of above - ....which led me to uninstall polyester through yast. When setting polyester for uninstall, all taboos where suddenly gone and I had to set the selected packages to be tabooed again.

Created attachment 574795 [details]
yast logfiles as of last comment 17.01

Reassigning to new maintainer.

just to let you know that this continues to be the case and happened today again.

Created attachment 576827 [details]
yast logs done right after the problem manifested. 

Again as before. Interesting this time that there were only security / recommended updates done, no packman or community repos involved. Hope that helps.

I have again the same problem as in the past here. Yast do not honor the tabooed package list anymore. This is always the case when beforehand I used Apper to install packages. But there is more. The permission to install software only after giving a root password twice is broken. It appears the following applies:
permission set to "secure"
Normal behavior: 
when you check with upper for software packages to update, this normally requieres to give the root password (to refresh resources).
Then the list of software is refreshed and updates are shown. 
Now, when you do want to install the software root password is required. But...

If in my system you do give three times erroneously the root password right now, apper tells you: user did not authorize action ....AND INSTALLS THE SOFTWARE FLAWLESSLY!
So you can now install on my 13.2 system whatever package without root through apper?? However this behaviour is not constant. It happened right now with Flashplayer. And it seems to be linked to the EULA agreement (although I have to check still if this is now the "standard" for all packages. 

Second anomaly: in yast tabooed packages are not all marked for install (as this was the case in 13.1. 

Third anomaly: the system is very slow when starting up KDE.

Forth: when starting up the system load is higher than before, although I do not have heavier software installed. 

Fifth: when all this happens one can note also the following: I have a multiuser system. Let us say user A, B, C. Always B and C are having KWin processes responsible for the system load as it seams. They reach 25% of CPU in a Corei5. When logging out from these two(!) users and logging in again, for a certain time the problem is gone. Then it reappears. 

I will reinstall the sytem soon but it would be nice to find out what causes this.

See bug report https://bugzilla.opensuse.org/show_bug.cgi?id=903632

Resolved: see bug 90324