qubes-dom0-update error

62 views
Skip to first unread message

tan...@tuta.io

unread,
Jun 4, 2018, 9:09:49 AM6/4/18
to Qubes Users
Was doing dom0 update for issue:

Got through Cleanup of all 84 updates.

Then receives a bunch of error messages regarding
"can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable)
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary: key 1 import failed."

That repeated 16 times. Then generated the grub configuration and reported updating , verifying and completing the update without further errors.

Is this error something that requires attention, fixing, or some other action on our part?

Thank you for your help.


------

tan...@tuta.io

unread,
Jul 21, 2018, 12:11:45 AM7/21/18
to Qubes Users

We've been running this node since then without rebooting.

If we reboot it, what are the chances that some vital functions of the OS will become unusable?

Thank you for your attention.

------



4. Jun 2018 13:09 by tan...@tuta.io:

awokd

unread,
Jul 25, 2018, 3:58:35 AM7/25/18
to tan...@tuta.io, Qubes Users
On Sat, July 21, 2018 4:11 am, tan...@tuta.io wrote:
>

> We've been running this node since then without rebooting.
>
>
> If we reboot it, what are the chances that some vital functions of the OS
> will become unusable? Thank you for your attention.
>
>
> ------
>
>
>
>
> 4. Jun 2018 13:09 by tan...@tuta.io <mailto:tan...@tuta.io>:
>
>
>
>> Was doing dom0 update for issue:
>> https://github.com/QubesOS/qubes-issues/issues/3500
>> <https://github.com/QubesOS/qubes-issues/issues/3500>
>>
>>
>> Got through Cleanup of all 84 updates.
>> Then receives a bunch of error messages regarding
>> "can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource
>> temporarily unavailable)>
>> /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary: key 1 import failed."
>> That repeated 16 times. Then generated the grub configuration and
>> reported updating , verifying and completing the update without further
>> errors. Is this error something that requires attention, fixing, or some
>> other action on our part? Thank you for your help.

This issue by itself didn't seem to hurt anything when I saw it on my
system. I managed to shoot myself in the foot on one when the update
process was taking a very long time with no feedback and I killed it. As
long as you didn't do that and let it run to completion, a reboot should
be OK.

Reply all
Reply to author
Forward
0 new messages