Yast modules always restart

jeancayron · May 22, 2011, 8:34pm

Hello,

I’ve got a weird problem since the update to 11.4: every time I use a yast module (the problem occurs with all of them), when I’ve finished (press OK or Cancel), it relaunch the module after the work is done. For example, launch the Package Manager, choice a package to install press OK : it performs the install and then relaunch the Package Manager. If you choose to quit, it will relaunch it… The only way to stop it to kill the process (or killx).

The same problem occurs with the terminal version of yast.

Has anyone an idea if it’s linked to a config file of yast under root or something so? I haven’t found such problems reported on the internet.

Any idea welcome.

Thanks.

jeancayron · May 27, 2011, 1:01pm

No one has an idea? Very anoying problem…

martin_helm · May 27, 2011, 1:17pm

jeancayron wrote:

>
> No one has an idea? Very anoying problem…
>
Start yast and go to the /etc/sysconfig editor, there is a setting in
system->yast2->gui named PKG_MGR_ACTION_AT_EXIT, change that from restart to
summary or close.

robin_listas · May 27, 2011, 1:50pm

On 2011-05-27 13:06, jeancayron wrote:
>
> No one has an idea? Very anoying problem…

Never seen that problem, sorry.
What method did you use for the upgrade?

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

jeancayron · May 30, 2011, 1:39pm

Thanks, I’ve tried. It’s already on “close”. But that occurs with all modules, not only with the package manager.

I think I upgraded with the DVD but I’m unsure, I’ve got two PC and I upgraded on or two of them with live upgrade. I might have use the liveupgrade for this one as well.

robin_listas · May 30, 2011, 3:33pm

On 2011-05-30 14:06, jeancayron wrote:

> robin_listas Wrote:
>> What method did you use for the upgrade?
>
> I think I upgraded with the DVD but I’m unsure, I’ve got two PC and I
> upgraded on or two of them with live upgrade. I might have use the
> liveupgrade for this one as well.

The DVD upgrade has a problem: it only upgrades the packages in the DVD,
not the rest; nor does it mark the rest for later upgrade. I opened a
bugzilla on this.

The proposed solution is to run a dup as well, after the upgrade. Or, you
can see with YaST what packages have not been upgraded and mark them.

What I do is run the code below:



rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
%{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
%{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}
" \
| sort | cut --fields="2-" --delimiter=\; \
| tee rpmlist.csv | less -S

or

rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" > rpmlist

which produces a list of all installed packages, sorted by date, with
interesting fields; in this case DISTRIBUTION and DISTTAG serves to find
packages from another distro version.

The first sample code produces a list to be imported into a spreadsheet,
the other is plain text.

So, with the list of obsolete packages in a terminal, I mark them one by
one in yast for update.

It is also possible that a “zypper up” could clear a lot of them. Zypper
dup is dangerous when you have several repos active.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

jeancayron · May 31, 2011, 10:23pm

Carlos, I sent you the result with a mail, it was to large for the forum.

I remember now, I first did a zypper up but then it failed and I continued the update with the DVD or the network install (I think network install).

robin_listas · May 31, 2011, 11:20pm

On 2011-05-31 22:36, jeancayron wrote:
>
> Carlos, I sent you the result with a mail, it was to large for the
> forum.

There was no need to send it to me, you can do this yourself. Or, you could
have used susepaste.

>
> I remember now, I first did a zypper up but then it failed and I
> continued the update with the DVD or the network install (I think
> network install).
>
>

You can see at the start of the file, a few packages for 11.3 and 11.2.
Probably not very important ones.

sem dec 26 2009 dju nôv 12 2009 qpitch
1.0.1-0.pm.1.1 x86_64 http://packman.links2linux.de
tongra@links2linux.de == main / openSUSE_11.2_Update (none)

vén mås 12 2010 mår mås 02 2010 guipdftk
0.33-1.10 x86_64 obs://build.opensuse.org/home:enzokiel(none) ==
home:enzokiel / openSUSE_11.2_Update (none)

With the DVD upgrade you would have more.

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

jeancayron · June 1, 2011, 8:49am

Thanks Albert,

qpitch is a tune (music) accorder, guipdftk is a program for editing pdfs.

In fact, I already checked the “orphaned packages” in Yast, so I doubt there are still packages to update.

The only thing that could happen is that the update deleted packages for problems of dependecies (I might have agreed it to go forward)…

I should maybe check the yast packages and pattern installed.

martin_helm · June 1, 2011, 12:15pm

jeancayron wrote:

> I should maybe check the yast packages and pattern installed.
>
You may all of them (yast packages) even if they already have the newest
version so that the dependcy resolver has a chance to check if something you
miss now has to be added or updated.
By the way, did you try “zypper verify” to check if anything is broken?

martin_helm · June 1, 2011, 12:23pm

martin_helm wrote:
> You may all of them (yast packages) even if they already have the newest
This shall be:
You may update all of them

robin_listas · June 1, 2011, 3:50pm

On 2011-06-01 09:06, jeancayron wrote:
>
> Thanks Albert,
>
> qpitch is a tune (music) accorder, guipdftk is a program for editing
> pdfs.
>
> In fact, I already checked the “orphaned packages” in Yast, so I doubt
> there are still packages to update.

Those two, and a few more, have to be updated: they belong to openSUSE
11.2. It is in the listing, the word “openSUSE_11.2_Update” means that.

> The only thing that could happen is that the update deleted packages
> for problems of dependecies (I might have agreed it to go forward)…

Possible.

Search in yast for the word “yast”, and check how all those packages are,
marked, not, updateable…

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)