Online Update y2base blocks

Greetings,

on an openSuse-13.2 I start yast/Online Update.

At some point installing the updates I see a message telling me ‘Updater is blocked by process nnnn’
Process nnnn is the yast2 process y2base.

I had to kill that process to finish the updater.
Is this a known problem or am I doing something wrong?

Running ‘zypper patch’ afterwards, no patches were installed; apparently all patches were marked processd/installed.

Thanks for hints,
Wolf

On 2015-07-21 10:46, WolfGrossi wrote:
>
> Greetings,
>
> on an openSuse-13.2 I start yast/Online Update.
>
> At some point installing the updates I see a message telling me ‘Updater
> is blocked by process nnnn’
> Process nnnn is the yast2 process y2base.
>
> I had to kill that process to finish the updater.
> Is this a known problem or am I doing something wrong?

No, I’ve never seen or heard of this.

What typically happens is that it refuses to start while packagekit is
running, offering to ask it to quit. Or try later, perhaps. But y2base
blocking, that’s new.

Guessing. Amongst the updates, was there some about yast itself?


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Well, you cannot use several package management applications at the same time.
If you want to use zypper, you have to quit YaST first, when zypper is running, you cannot use YaST, and so on.

The “Updater” that was blocked was probably the desktop’s update applet that wanted to check for updates.
You shouldn’t have killed YaST, that’s a dangerous thing to do when it is installing updates.

Next time, just ignore the message, or use the updater to install the updates in the first place.

What made you think I run other package management applications at the same time?
Read my post, I said ‘I started yast online update … and afterwards …’

Guessing. Amongst the updates, was there some about yast itself?

No, the machine was cleanly booted add ‘yast/onlouine update’ was the only activity.

Cheers
Wolf

On 2015-07-21 11:56, WolfGrossi wrote:
>
>>
>> Guessing. Amongst the updates, was there some about yast itself?
>>
>
> No, the machine was cleanly booted add ‘yast/onlouine update’ was the
> only activity.

No, I mean that in yast online update, in the list of packages that were
going to be updated, there was something related to yast itself?


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

This was just a general explanation.

Again, to me it sounds like you ran YaST Online update, and while that was installing updates the desktop’s updater wanted to check for updates. As YaST was running (and installing updates), it couldn’t and notified you about the fact.
To prevent that, just use the updater to install the update. Or disable it if you prefer YaST. Or ignore that message.

And I also want to stress again that you never should kill YaST or any other package management application while it is installing updates.

OK, thanks for your comments.

If the issue happens the next time I’ll gonna provide a process list.

Thanks and have a nice day,
Wolf

That’s unnecessary and won’t show anything interesting.

The case is clear IMHO:

  • you ran YaST->Online Update, which (process y2base in particular) blocked the package management
  • while it was running, the desktop’s updater (which uses packagekitd) tried to check for updates but couldn’t because y2base blocked the package management

You would only see y2base in the process list, because packagekitd would already have quit because it couldn’t access the package management.

Btw, the desktop’s updater normally checks for updates once a day. But it does a first check 5 minutes after login.
As you said you ran YaST directly after login, that’s even more likely to be exactly what actually happened.

I have seen that. I have just ignored it.

I use KDE. I think it is Apper trying to check for updates, but blocked by Yast. It will try again when Yast finishes. It’s nothing to worry about. But I’ll admit that the message can be a bit confusing.

On 2015-07-21 13:26, wolfi323 wrote:

> The case is clear IMHO:
>
> - you ran YaST->Online Update, which (process y2base in particular)
> blocked the package management
> - while it was running, the desktop’s updater (which uses packagekitd)
> tried to check for updates but couldn’t because y2base blocked the
> package management

Ah. Ok, so it was packagekit complaining that it was blocked by yast,
not YOU complaining about yast2. Then just ignore the message :slight_smile:

> Btw, the desktop’s updater normally checks for updates once a day. But
> it does a first check 5 minutes after login.
> As you said you ran YaST directly after login, that’s even more likely
> to be exactly what actually happened.

Yep.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))