[Solved] Stuck at "configuring grub-pc (amd64)"

verycd · Post by **verycd** » Mon Feb 22, 2021 2:32 pm

Hi there,
I have been waiting for the software updating process to finish for an hour. It seems to hang at "configuring grub-pc (am64)". Please see below and advise what I should do next.
Thanks a lot.

Preconfiguring packages ...
(Reading database ... 462126 files and directories currently installed.)
Preparing to unpack .../libgdk-pixbuf2.0-common_2.40.0+dfsg-3ubuntu0.2_all.deb ...
Unpacking libgdk-pixbuf2.0-common (2.40.0+dfsg-3ubuntu0.2) over (2.40.0+dfsg-3ubuntu0.1) ...
Setting up libgdk-pixbuf2.0-common (2.40.0+dfsg-3ubuntu0.2) ...
(Reading database ... 462126 files and directories currently installed.)
Preparing to unpack .../libgdk-pixbuf2.0-0_2.40.0+dfsg-3ubuntu0.2_amd64.deb ...
De-configuring libgdk-pixbuf2.0-0:i386 (2.40.0+dfsg-3ubuntu0.1) ...
Unpacking libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-3ubuntu0.2) over (2.40.0+dfsg-3ubuntu0.1) ...
Preparing to unpack .../libgdk-pixbuf2.0-0_2.40.0+dfsg-3ubuntu0.2_i386.deb ...
Unpacking libgdk-pixbuf2.0-0:i386 (2.40.0+dfsg-3ubuntu0.2) over (2.40.0+dfsg-3ubuntu0.1) ...
Preparing to unpack .../gir1.2-gdkpixbuf-2.0_2.40.0+dfsg-3ubuntu0.2_amd64.deb ...
Unpacking gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.2) over (2.40.0+dfsg-3ubuntu0.1) ...
Setting up libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-3ubuntu0.2) ...
Setting up gir1.2-gdkpixbuf-2.0:amd64 (2.40.0+dfsg-3ubuntu0.2) ...
(Reading database ... 462126 files and directories currently installed.)
Preparing to unpack .../libldap-common_2.4.49+dfsg-2ubuntu1.7_all.deb ...
Unpacking libldap-common (2.4.49+dfsg-2ubuntu1.7) over (2.4.49+dfsg-2ubuntu1.6) ...
Setting up libldap-common (2.4.49+dfsg-2ubuntu1.7) ...
(Reading database ... 462126 files and directories currently installed.)
Preparing to unpack .../0-libldap-2.4-2_2.4.49+dfsg-2ubuntu1.7_amd64.deb ...
De-configuring libldap-2.4-2:i386 (2.4.49+dfsg-2ubuntu1.6) ...
Unpacking libldap-2.4-2:amd64 (2.4.49+dfsg-2ubuntu1.7) over (2.4.49+dfsg-2ubuntu1.6) ...
Preparing to unpack .../1-libldap-2.4-2_2.4.49+dfsg-2ubuntu1.7_i386.deb ...
Unpacking libldap-2.4-2:i386 (2.4.49+dfsg-2ubuntu1.7) over (2.4.49+dfsg-2ubuntu1.6) ...
Preparing to unpack .../2-grub-pc_2.04-1ubuntu26.9_amd64.deb ...
Unpacking grub-pc (2.04-1ubuntu26.9) over (2.04-1ubuntu26.

...
Preparing to unpack .../3-grub2-common_2.04-1ubuntu26.9_amd64.deb ...
Unpacking grub2-common (2.04-1ubuntu26.9) over (2.04-1ubuntu26.

...
Preparing to unpack .../4-grub-pc-bin_2.04-1ubuntu26.9_amd64.deb ...
Unpacking grub-pc-bin (2.04-1ubuntu26.9) over (2.04-1ubuntu26.

...
Preparing to unpack .../5-grub-efi-amd64-signed_1.142.11+2.04-1ubuntu26.9_amd64.deb ...
Unpacking grub-efi-amd64-signed (1.142.11+2.04-1ubuntu26.9) over (1.142.10+2.04-1ubuntu26.

...
Preparing to unpack .../6-grub-efi-amd64-bin_2.04-1ubuntu26.9_amd64.deb ...
Unpacking grub-efi-amd64-bin (2.04-1ubuntu26.9) over (2.04-1ubuntu26.

...
Preparing to unpack .../7-grub-common_2.04-1ubuntu26.9_amd64.deb ...
Unpacking grub-common (2.04-1ubuntu26.9) over (2.04-1ubuntu26.

...
Preparing to unpack .../8-libgdk-pixbuf2.0-bin_2.40.0+dfsg-3ubuntu0.2_amd64.deb ...
Unpacking libgdk-pixbuf2.0-bin (2.40.0+dfsg-3ubuntu0.2) over (2.40.0+dfsg-3ubuntu0.1) ...
Setting up libldap-2.4-2:amd64 (2.4.49+dfsg-2ubuntu1.7) ...
Setting up libldap-2.4-2:i386 (2.4.49+dfsg-2ubuntu1.7) ...
Setting up grub-common (2.04-1ubuntu26.9) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up libgdk-pixbuf2.0-0:i386 (2.40.0+dfsg-3ubuntu0.2) ...
Setting up libgdk-pixbuf2.0-bin (2.40.0+dfsg-3ubuntu0.2) ...
Processing triggers for ubuntu-system-adjustments (2020.12.28) ...
Reloading systemd
Removed /etc/systemd/system/multi-user.target.wants/hddtemp.service.
Created symlink /etc/systemd/system/multi-user.target.wants/hddtemp.service → /etc/systemd/system/hddtemp.service.
Processing triggers for install-info (6.7.0.dfsg.2-5) ...
Setting up grub-efi-amd64-bin (2.04-1ubuntu26.9) ...
Setting up grub2-common (2.04-1ubuntu26.9) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
Processing triggers for systemd (245.4-4ubuntu3.4) ...
Processing triggers for man-db (2.9.1-1) ...
Setting up grub-pc-bin (2.04-1ubuntu26.9) ...
Setting up grub-pc (2.04-1ubuntu26.9) ...
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-65-generic
Found initrd image: /boot/initrd.img-5.4.0-65-generic
Found linux image: /boot/vmlinuz-5.4.0-64-generic
Found initrd image: /boot/initrd.img-5.4.0-64-generic
Found linux image: /boot/vmlinuz-5.4.0-58-generic
Found initrd image: /boot/initrd.img-5.4.0-58-generi

AnonymousFighter · Post by **AnonymousFighter** » Tue Feb 23, 2021 5:09 am

Revert with timeshift and don't update again.
Even better reinstall.

verycd · Post by **verycd** » Tue Feb 23, 2021 10:08 am

Thank you. I didn't turn off the pc. The updating can't be closed. Is this update crutial that the system must have? By "reinstall", do you mean Mint itself? Can I be assured that this kind of update issue is not caused by hardware incompability that will persist?

BTW, by "the updating can't be closed", I mean the window that showing the process bar and detailed process can't be closed with the process bar stuck at 90%. However, when I closed the update manager and reopened it, it shows my system is up to date. Is there a way to verify that the grub-pc(amd64) is successfully configured?

SMG · Post by **SMG** » Tue Feb 23, 2021 11:24 am

verycd wrote: ↑
Tue Feb 23, 2021 10:08 am
BTW, by "the updating can't be closed", I mean the window that showing the process bar and detailed process can't be closed with the process bar stuck at 90%. However, when I closed the update manager and reopened it, it shows my system is up to date. Is there a way to verify that the grub-pc(amd64) is successfully configured?

Reinstalling is an extremely drastic move to take at this point in time and I do not see a need to do it given the system is still working. Grub changes will take effect the next time you boot.

Make sure you have your personal data backed up (which is always a good thing to do).

How many kernels do you have installed? You can check in Update Manager. Select View > Linux Kernels and click Continue. You have not supplied any information about your system, so I do not know what kernels you might have installed. Recommendation is to have the currently in use kernel and one or two older ones.

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

verycd · Post by **verycd** » Tue Feb 23, 2021 1:05 pm

Please see the install information of my system. I encounterered a similar issue a weeks ago. Can't recall what update it was. I powered off the PC manually to close update manager and was given the notice that update had been interrupted but subsequent reinstall the same update was successful. This time I was able to close the update manager from the taskbar and update seems successful (except the progress window stopped at around 90% and became irresponsive). I was wondering maybe the update progress window halted and went dead because I was running virtualbox.

Kernels:

Not sure why the image tool did not work. Here is the direct link:
https://ibb.co/PcJmchJ

Code: Select all

System:
  Kernel: 5.4.0-65-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: HP product: HP EliteDesk 800 G2 SFF v: N/A 
  serial: <filter> Chassis: type: 4 serial: <filter> 
  Mobo: HP model: 8054 v: KBC Version 05.39 serial: <filter> UEFI: HP 
  v: N01 Ver. 02.51 date: 10/19/2020 
Battery:
  Device-1: hidpp_battery_0 model: Logitech K350 serial: <filter> 
  charge: 70% (should be ignored) rechargeable: yes status: Discharging 
  Device-2: hidpp_battery_1 
  model: Logitech Wireless Illuminated Keyboard K800 serial: <filter> 
  charge: 50% (should be ignored) rechargeable: yes status: N/A 
  Device-3: hidpp_battery_2 model: Logitech Wireless Mouse M510 
  serial: <filter> charge: 55% (should be ignored) rechargeable: yes 
  status: Discharging 
CPU:
  Topology: Quad Core model: Intel Core i7-6700 bits: 64 type: MT MCP 
  arch: Skylake-S rev: 3 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 54398 
  Speed: 1600 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 1600 2: 1600 
  3: 1597 4: 1600 5: 1600 6: 1600 7: 1600 8: 1600 
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Hewlett-Packard driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:1912 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 3840x2160~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
  chip ID: 8086:a170 
  Sound Server: ALSA v: k5.4.0-65-generic 
Network:
  Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e 
  v: 3.2.6-k port: efa0 bus ID: 00:1f.6 chip ID: 8086:15b7 
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: anbox0 state: up speed: N/A duplex: N/A mac: <filter> 
  IF-ID-2: lxcbr0 state: down mac: <filter> 
  IF-ID-3: vboxnet0 state: down mac: <filter> 
  IF-ID-4: vethEWK8ER state: up speed: 10000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 10.92 TiB used: 4.52 TiB (41.4%) 
  ID-1: /dev/sda type: USB vendor: Seagate model: BUP Portable 
  size: 3.64 TiB serial: <filter> rev: 1707 scheme: GPT 
  ID-2: /dev/sdb type: USB vendor: Western Digital model: WD20EARX-00PASB0 
  size: 1.82 TiB serial: <filter> rev: 2021 scheme: MBR 
  ID-3: /dev/sdc type: USB vendor: Western Digital model: WD20EARS-07MVWB0 
  size: 1.82 TiB serial: <filter> rev: 2021 scheme: MBR 
  ID-4: /dev/sdd model: HAJAAN HS1TBE 1TB size: 931.51 GiB speed: 6.0 Gb/s 
  serial: <filter> rev: 1A0 scheme: GPT 
  ID-5: /dev/sde vendor: Western Digital model: WD10EZEX-08WN4A0 
  size: 931.51 GiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 1A01 scheme: MBR 
  ID-6: /dev/sdf vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 0001 scheme: GPT 
Partition:
  ID-1: / size: 915.40 GiB used: 361.37 GiB (39.5%) fs: ext4 dev: /dev/sdd2 
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
  1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/megasync.list 
  1: deb https://mega.nz/linux/MEGAsync/xUbuntu_20.04/ ./
  Active apt repos in: /etc/apt/sources.list.d/official-dbgsym-repositories.list 
  1: deb http://ddebs.ubuntu.com focal main restricted universe multiverse
  2: deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://mirror.csclub.uwaterloo.ca/linuxmint-packages ulyssa main upstream import backport
  2: deb http://archive.ubuntu.mirror.rafal.ca/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.mirror.rafal.ca/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.mirror.rafal.ca/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/official-source-repositories.list 
  1: deb-src http://mirror.csclub.uwaterloo.ca/linuxmint-packages ulyssa main upstream import backport
  2: deb-src http://archive.ubuntu.mirror.rafal.ca/ubuntu focal main restricted universe multiverse
  3: deb-src http://archive.ubuntu.mirror.rafal.ca/ubuntu focal-updates main restricted universe multiverse
  4: deb-src http://archive.ubuntu.mirror.rafal.ca/ubuntu focal-backports main restricted universe multiverse
  5: deb-src http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb-src http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/spotify.list 
  1: deb http://repository.spotify.com stable non-free
Info:
  Processes: 476 Uptime: 7d 16h 01m Memory: 31.25 GiB 
  used: 25.23 GiB (80.7%) Init: systemd v: 245 runlevel: 5 Compilers: 
  gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal 
  inxi: 3.0.38

SMG · Post by **SMG** » Tue Feb 23, 2021 2:29 pm

verycd wrote: ↑
Tue Feb 23, 2021 1:05 pm
Kernels:

Not sure why the image tool did not work. Here is the direct link:
https://ibb.co/PcJmchJ

Next time you try this, you need to click on the 5.4 on the left panel to see what kernels you have installed. The 5.8 kernels are available to install and thus this screen defaulted to the highest number (5.8 ) rather than the 5.4 kernels you have installed. When you click 5.4, you will see which kernel is "Active" and which ones are "Installed". The 5.4 kernel is the LTS kernel and should run well on your system. The 5.8 kernel has a short-term life and is really only there for people with very new equipment who need newer drivers.

If you have more than a few older 5.4 kernels, you can click on the kernel number and a remove button will appear.

I do not see anything in your inxi information which might indicate an issue. You are running on a spinning disk HDD rather than an SSD, so it might take a bit longer for updates to happen depending upon what else is running on your system at the time.

verycd · Post by **verycd** » Tue Feb 23, 2021 2:54 pm

So I can remove the two "installed" 5.4 kernels and keep only the "active" 5.4.0-65? Please see the screen shots.

Are you sure the Mint in running on an HDD? I installed it on (ID-4) the 1TB SSD. Have I been fooled all the time?

5.4 kernels
https://ibb.co/Q6PKkL6
5.8 kernels
https://ibb.co/gjkF7Cy

SMG · Post by **SMG** » Tue Feb 23, 2021 3:11 pm

verycd wrote: ↑
Tue Feb 23, 2021 2:54 pm
So I can remove the two "installed" 5.4 kernels and keep only the "active" 5.4.0-65? Please see the screen shots.

I personally keep the "Installed" and one older version. Sometimes changes in the kernel can cause problems to appear, so it's a good idea to keep at least one older version installed that you know runs well on your system. Sometimes the backports/fixes on the newer kernels can cause issues for some hardware. If you have an older kernel installed, you can boot into the older kernel and remove the newer one until whatever caused the problem is fixed.

verycd wrote: ↑
Tue Feb 23, 2021 2:54 pm
Are you sure the Mint in running on an HDD? I installed it on (ID-4) the 1TB SSD. Have I been fooled all the time?

My error. (I didn't wrap my eyes around to the next line to see there was no rotation after the 6.0Gb/s.) You are correct.

verycd · Post by **verycd** » Tue Feb 23, 2021 3:39 pm

Thanks. Since I have space on the drive, I will keep both installed kernels as backup for the active one.

BTW, does the update manager take care of all packages installed in the system or only selective ones? In not all, what is the easiest way to find out which package needs me to uninstall, manually downlond and reinstall the newest version? I am asking because some packages in the repository are outdated. For instance, the pianobooster, I left a note in my review a few days ago but it is still the same old version today. Where should I report on an outdated package?

SMG · Post by **SMG** » Tue Feb 23, 2021 4:07 pm

verycd wrote: ↑
Tue Feb 23, 2021 3:39 pm
BTW, does the update manager take care of all packages installed in the system or only selective ones? In not all, what is the easiest way to find out which package needs me to uninstall, manually downlond and reinstall the newest version? I am asking because some packages in the repository are outdated. For instance, the pianobooster, I left a note in my review a few days ago but it is still the same old version today. Where should I report on an outdated package?

Update Manager will alert you to updates when they become available in the Ubuntu repositories. The versions available in the repositories are the ones known to work on Mint.

For example, I just received notification today in Update Manager of Thunderbird 78 being available (I've been patiently waiting for it!). Yet Thunderbird 78 has been available for many months. I could have gone through all the extra steps to install it earlier, but I decided to wait for the repository version. It was an easy one-click upgrade from Thunderbird 68 by using the repository version. It had to undergo quite a bit of testing and triage before being available in the repository which is why it was "behind" when it was originally released, but I trust this version will work well with my install.

You received replies with links to information on your other thread regarding pianobooster.

verycd · Post by **verycd** » Tue Feb 23, 2021 4:31 pm

Good to know the repository is looked after and new versions may be still under scrutity. I will take your advice!

verycd · Post by **verycd** » Tue Feb 23, 2021 6:51 pm

Unfortunately, it is happening again with the new 5.0.4-66 kernel update. Please see the screenshot.

https://ibb.co/1mRzbTg

I can't "Select View > Linux Kernels and click Continue" because the above window is not responsive - something is running or dead.

SMG · Post by **SMG** » Tue Feb 23, 2021 8:05 pm

verycd wrote: ↑
Tue Feb 23, 2021 6:51 pm
Unfortunately, it is happening again with the new 5.0.4-66 kernel update. Please see the screenshot.

https://ibb.co/1mRzbTg

I can't "Select View > Linux Kernels and click Continue" because the above window is not responsive - something is running or dead.

If Update Manger is still running, I would not expect that you could select View or do anything else with the app.

Were you running virtualbox? I noticed on the inxi information you posted earlier in the thread that even though your system has quite a lot of memory, you were using most of it.
Info:
Processes: 476 Uptime: 7d 16h 01m Memory: 31.25 GiB
used: 25.23 GiB (80.7%) Init: systemd v: 245 runlevel: 5 Compilers:
gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal
inxi: 3.0.38

Although I have not experienced it, others have noticed Cinnamon processes seem to start taking a lot of memory over time. People are restarting Cinnamon using Ctl-Alt-Escape to reduce the memory load. Maybe your system is experiencing it and that will help?

verycd · Post by **verycd** » Tue Feb 23, 2021 10:38 pm

I think I asigned at least 10G of ram to the virtual box and often keep many tabs open in Linux. But still, I doubt the update should take more than a few minutes. Two hours later the progress remained the same. I then "closed" the update manager from the task bar. The dead window didn't disappear with the manager and the "close" button doesn't function. I "restarted" update manager and saw it hadn't actually been killed. Still couldn't click "view". I didn't not notice any lag while performing other tasks but I decided to close all web browsers. Please see the system load after that in the graphic below.

https://ibb.co/BP1Pb5L

The update manager is still not working. Since update manager is hanging, do you suggest that I perform Ctl-Alt-Escape now to restart Cinnoman? I suppose the updating process has already been interrupted any way by some unknown issue, can't be terminated by regular means, and won't recover again.

P.S. not sure if the following info helps diagnosis
https://ibb.co/pvvqcYg
https://ibb.co/CwbX2NP
The "mintUpdate" process is using 0 CPU and 31.5MB RAM now.

verycd · Post by **verycd** » Tue Feb 23, 2021 11:06 pm

I clicked "New Window" in the Update Manager menu in the task bar, a new window appeared with "your system is up to date" notice but when I clicked "refresh", another message came up. Please see the screenshot below:

https://ibb.co/6NxsvDX

What other process could be using "the package management system"? If it is the previous task of the update manager then the update process has not finished. Yet, the new update manager window shows "your system is up to date". If it is not, then the update progress window shouldn't be hanging there. From the new update manager window I went to - view -kernel- continue, and got the following kernel status:

https://ibb.co/GvRMqTT

And update history:

https://ibb.co/Xp9CrcP

verycd · Post by **verycd** » Wed Feb 24, 2021 7:13 am

The PC didn't go to sleep mode the whole night (set to 2 hours of idling). Now I can perform "refresh" in the Update Manager without the "package management system being used" warning. A firefox update was done this morning. The system is shown as up to date but the newly installed 5.4.0-66 for some reason is not shown "active" - the 65 does. Will it become active only after a reboot?

https://ibb.co/LRKCGXs

I still wonder what had been using the package management system for so many hours and if this extreme slow down will happen every time when there is a kernel update.

P.S.
Good heavens. Just opened the Update Manager and clicked the "refresh" icon, there reappeared the message "Cannot Procreed. Another process is currently using the package management system. Please wait for it to finish and then try again".

SMG · Post by **SMG** » Wed Feb 24, 2021 12:46 pm

verycd wrote: ↑
Wed Feb 24, 2021 7:13 am
The system is shown as up to date but the newly installed 5.4.0-66 for some reason is not shown "active" - the 65 does. Will it become active only after a reboot?

Correct. The system can only use one kernel at a time. Kernels are activated upon system reboot.

verycd wrote: ↑
Wed Feb 24, 2021 7:13 am
Good heavens. Just opened the Update Manager and clicked the "refresh" icon, there reappeared the message "Cannot Proceed. Another process is currently using the package management system. Please wait for it to finish and then try again".

And there is no kernel update happening right now, because you did get the indication the prior one finished. Update Manager defaults are set to check for updates once every two hours.

In Update Manager I just clicked Edit > Information. It is a log of sorts. Maybe something there will give a clue as to what is happening.

The only other idea I have right now is maybe somehow this is an internet connection related issue? Update Manager does need to contact whichever mirror you are using. Maybe that is a factor.

verycd · Post by **verycd** » Wed Feb 24, 2021 1:10 pm

Before rebooting the system, I clicked View - Information in Update Manager:

Code: Select all

02.23@22:00 ++ Launching Update Manager
02.23@22:00 ++ Changes to the package cache detected, triggering refresh
02.23@22:00 ++ Starting refresh (local only)
02.23@22:00 ++ Initial refresh will happen in 0 day(s), 0 hour(s) and 10 minute(s)
02.23@22:00 ++ System is up to date
02.23@22:00 ++ Refresh finished
02.23@22:10 ++ Update Manager window is open, skipping initial refresh
02.23@22:10 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:11 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:12 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:13 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:14 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:15 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:16 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:17 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:18 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:19 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:20 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:21 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:22 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:23 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:24 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:25 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:26 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:27 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:28 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:29 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:30 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:31 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:32 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:33 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:34 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:35 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:36 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:37 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:38 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:39 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:40 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:41 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:52 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:53 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:54 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:55 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:56 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:57 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@22:58 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@22:59 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:00 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:01 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:02 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:03 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:04 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:05 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:06 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:07 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:08 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:09 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:10 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:11 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:12 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:13 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:14 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:15 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:16 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:17 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:18 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:19 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:20 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:21 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:22 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:23 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:24 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:25 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:26 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:27 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:28 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:29 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:30 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:31 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:32 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:33 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:34 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:35 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:36 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:37 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:38 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:39 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:40 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:41 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:42 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:43 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:44 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:45 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:46 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:47 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:48 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:49 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:50 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:51 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:52 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:53 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:54 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:55 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:56 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:57 ++ Update Manager window is open, delaying recurring refresh by 60s
02.23@23:58 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.23@23:59 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:00 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:01 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:02 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:03 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:04 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:05 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:06 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:07 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:08 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:09 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:10 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:11 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:12 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:13 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:14 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:15 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:16 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:17 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:18 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:19 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:20 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:21 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:22 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:23 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:25 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:26 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:27 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:28 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:29 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:30 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:31 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:32 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:33 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:34 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:35 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:36 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:37 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:38 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:39 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:40 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:41 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:42 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:43 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:44 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:45 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:46 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:47 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:48 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:49 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:50 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:51 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:52 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:53 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:54 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:55 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:56 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:57 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@00:58 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@00:59 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:00 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:01 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:02 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:03 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:04 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:05 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:06 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:07 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:08 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:09 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:10 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:11 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:12 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:13 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:14 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:15 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:16 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:17 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:18 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:19 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:20 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:21 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:22 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:23 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:24 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:25 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:26 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:27 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:28 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:29 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:30 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:31 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:32 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:33 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:34 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:35 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:36 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:37 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:38 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:39 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:40 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:41 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:42 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:43 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:44 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:45 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:46 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:47 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:48 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:49 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:50 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:51 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:52 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:53 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:54 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:55 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:56 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:57 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@01:58 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@01:59 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:00 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:01 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:02 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:03 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:04 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:05 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:06 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:07 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:08 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:09 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:10 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:11 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:12 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:13 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:14 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:15 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:16 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:17 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:18 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:19 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:20 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:21 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:22 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:23 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:24 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:25 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:26 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:27 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:28 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:29 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:30 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:31 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:32 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:33 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:34 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:35 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:36 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:37 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:38 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:39 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:40 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:41 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:42 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:43 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:44 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:45 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:46 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:47 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:48 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:49 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:50 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:51 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:52 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:53 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:54 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:55 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:56 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:57 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@02:58 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@02:59 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:00 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:01 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:02 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:03 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:04 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:05 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:06 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:07 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:08 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:09 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:10 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:11 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:12 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:13 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:14 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:15 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:16 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:17 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:18 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:19 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:20 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:21 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:22 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:23 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:24 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:25 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:26 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:27 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:28 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:29 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:30 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:31 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:32 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:33 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:34 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:35 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:36 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:37 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:38 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:39 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:40 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:41 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:42 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:43 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:44 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:45 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:46 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:47 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:48 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:49 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:50 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:51 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:52 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:53 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:54 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:55 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:56 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:57 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@03:58 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@03:59 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:00 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:01 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:02 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:03 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:04 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:05 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:06 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:07 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:08 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:09 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:10 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:11 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:12 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:13 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:14 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:15 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:16 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:17 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:18 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:19 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:20 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:21 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:22 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:23 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:24 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:26 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:27 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:28 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:29 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:30 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:31 ++ Changes to the package cache detected, triggering refresh
02.24@04:31 ++ Starting refresh (local only)
02.24@04:31 ++ System is up to date
02.24@04:31 ++ Refresh finished
02.24@04:31 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:32 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:33 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:34 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:35 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:36 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:37 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:38 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:39 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:40 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:41 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:42 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:43 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:44 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:45 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:46 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:47 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:48 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:49 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:50 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:51 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:52 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:53 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:54 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:55 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:56 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:57 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@04:58 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@04:59 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:00 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:01 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:02 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:03 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:04 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:05 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:06 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:07 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:08 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:09 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:10 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:11 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:12 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:13 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:14 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:15 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:16 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:17 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:18 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:19 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:20 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:21 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:22 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:23 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:24 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:25 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:26 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:27 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:28 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:29 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:30 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:31 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:32 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:33 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:34 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:35 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:36 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:37 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:38 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:39 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:40 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:41 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:42 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:43 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:44 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:45 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:46 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:47 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:48 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:49 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:50 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:51 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:52 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:53 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:54 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:55 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:56 ++ Recurring refresh will happen in 0 day(s), 0 hour(s) and 1 minute(s)
02.24@05:57 ++ Update Manager window is open, delaying recurring refresh by 60s
02.24@05:58 ++ Starting refresh (retrieving lists of updates from remote servers)
02.24@05:58 ++ Found 1 software updates
02.24@05:58 ++ Refresh finished
02.24@05:58 ++ Install requested by user
02.24@05:58 ++ Will install firefox-locale-en
02.24@05:58 ++ Will install firefox-locale-fr
02.24@05:58 ++ Will install firefox-locale-ru
02.24@05:58 ++ Will install firefox
02.24@05:58 ++ Ready to launch synaptic
02.24@05:58 ++ Recurring refresh will happen in 0 day(s), 1 hour(s) and 59 minute(s)

(synaptic:429362): Gtk-CRITICAL **: 05:58:38.153: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
02.24@05:59 ++ Return code:0
02.24@05:59 ++ Install finished
02.24@05:59 ++ Starting refresh (local only)
02.24@05:59 ++ System is up to date
02.24@05:59 ++ Refresh finished
02.24@06:00 ++ Starting refresh (retrieving lists of updates from remote servers)
02.24@06:00 ++ System is up to date
02.24@06:00 ++ Refresh finished
02.24@07:58 ++ Update Manager is in tray mode, performing recurring refresh
02.24@07:58 ++ Package management system locked by another process, retrying in 60s
02.24@07:59 ++ Package management system locked by another process, retrying in 60s
02.24@08:00 ++ Package management system locked by another process, retrying in 60s
02.24@08:01 ++ Package management system locked by another process, retrying in 60s
02.24@08:02 ++ Package management system locked by another process, retrying in 60s
02.24@08:03 ++ Package management system locked by another process, retrying in 60s
02.24@08:04 ++ Package management system locked by another process, retrying in 60s
02.24@08:05 ++ Package management system locked by another process, retrying in 60s
02.24@08:06 ++ Package management system locked by another process, retrying in 60s
02.24@08:07 ++ Package management system locked by another process, retrying in 60s
02.24@08:08 ++ Package management system locked by another process, retrying in 60s
02.24@08:09 ++ Package management system locked by another process, retrying in 60s
02.24@08:10 ++ Package management system locked by another process, retrying in 60s
02.24@08:11 ++ Package management system locked by another process, retrying in 60s
02.24@08:12 ++ Package management system locked by another process, retrying in 60s
02.24@08:13 ++ Package management system locked by another process, retrying in 60s
02.24@08:14 ++ Package management system locked by another process, retrying in 60s
02.24@08:15 ++ Package management system locked by another process, retrying in 60s
02.24@08:16 ++ Package management system locked by another process, retrying in 60s
02.24@08:17 ++ Package management system locked by another process, retrying in 60s
02.24@08:18 ++ Package management system locked by another process, retrying in 60s
02.24@08:19 ++ Package management system locked by another process, retrying in 60s
02.24@08:20 ++ Package management system locked by another process, retrying in 60s
02.24@08:21 ++ Package management system locked by another process, retrying in 60s
02.24@08:22 ++ Package management system locked by another process, retrying in 60s
02.24@08:23 ++ Package management system locked by another process, retrying in 60s
02.24@08:24 ++ Package management system locked by another process, retrying in 60s
02.24@08:25 ++ Package management system locked by another process, retrying in 60s
02.24@08:26 ++ Package management system locked by another process, retrying in 60s
02.24@08:27 ++ Package management system locked by another process, retrying in 60s
02.24@08:28 ++ Package management system locked by another process, retrying in 60s
02.24@08:29 ++ Package management system locked by another process, retrying in 60s
02.24@08:30 ++ Package management system locked by another process, retrying in 60s
02.24@08:31 ++ Package management system locked by another process, retrying in 60s
02.24@08:32 ++ Package management system locked by another process, retrying in 60s
02.24@08:33 ++ Package management system locked by another process, retrying in 60s
02.24@08:34 ++ Package management system locked by another process, retrying in 60s
02.24@08:35 ++ Package management system locked by another process, retrying in 60s
02.24@08:36 ++ Package management system locked by another process, retrying in 60s
02.24@08:37 ++ Package management system locked by another process, retrying in 60s
02.24@08:38 ++ Package management system locked by another process, retrying in 60s
02.24@08:39 ++ Package management system locked by another process, retrying in 60s
02.24@08:40 ++ Package management system locked by another process, retrying in 60s
02.24@08:41 ++ Package management system locked by another process, retrying in 60s
02.24@08:42 ++ Package management system locked by another process, retrying in 60s
02.24@08:43 ++ Package management system locked by another process, retrying in 60s
02.24@08:44 ++ Package management system locked by another process, retrying in 60s
02.24@08:45 ++ Package management system locked by another process, retrying in 60s
02.24@08:46 ++ Package management system locked by another process, retrying in 60s
02.24@08:47 ++ Package management system locked by another process, retrying in 60s
02.24@08:48 ++ Package management system locked by another process, retrying in 60s
02.24@08:49 ++ Package management system locked by another process, retrying in 60s
02.24@08:50 ++ Package management system locked by another process, retrying in 60s
02.24@08:51 ++ Package management system locked by another process, retrying in 60s
02.24@08:52 ++ Package management system locked by another process, retrying in 60s
02.24@08:53 ++ Package management system locked by another process, retrying in 60s
02.24@08:54 ++ Package management system locked by another process, retrying in 60s
02.24@08:55 ++ Package management system locked by another process, retrying in 60s
02.24@08:56 ++ Package management system locked by another process, retrying in 60s
02.24@08:57 ++ Package management system locked by another process, retrying in 60s
02.24@08:58 ++ Package management system locked by another process, retrying in 60s
02.24@08:59 ++ Package management system locked by another process, retrying in 60s
02.24@09:00 ++ Package management system locked by another process, retrying in 60s
02.24@09:01 ++ Package management system locked by another process, retrying in 60s
02.24@09:02 ++ Package management system locked by another process, retrying in 60s
02.24@09:03 ++ Package management system locked by another process, retrying in 60s
02.24@09:04 ++ Package management system locked by another process, retrying in 60s
02.24@09:05 ++ Package management system locked by another process, retrying in 60s
02.24@09:06 ++ Package management system locked by another process, retrying in 60s
02.24@09:07 ++ Package management system locked by another process, retrying in 60s
02.24@09:08 ++ Package management system locked by another process, retrying in 60s
02.24@09:09 ++ Package management system locked by another process, retrying in 60s
02.24@09:10 ++ Package management system locked by another process, retrying in 60s
02.24@09:11 ++ Package management system locked by another process, retrying in 60s
02.24@09:12 ++ Package management system locked by another process, retrying in 60s
02.24@09:13 ++ Package management system locked by another process, retrying in 60s
02.24@09:14 ++ Package management system locked by another process, retrying in 60s
02.24@09:15 ++ Package management system locked by another process, retrying in 60s
02.24@09:16 ++ Package management system locked by another process, retrying in 60s
02.24@09:17 ++ Package management system locked by another process, retrying in 60s
02.24@09:18 ++ Package management system locked by another process, retrying in 60s
02.24@09:19 ++ Package management system locked by another process, retrying in 60s
02.24@09:20 ++ Package management system locked by another process, retrying in 60s
02.24@09:21 ++ Package management system locked by another process, retrying in 60s
02.24@09:22 ++ Package management system locked by another process, retrying in 60s
02.24@09:23 ++ Package management system locked by another process, retrying in 60s
02.24@09:24 ++ Package management system locked by another process, retrying in 60s
02.24@09:25 ++ Package management system locked by another process, retrying in 60s
02.24@09:26 ++ Package management system locked by another process, retrying in 60s
02.24@09:27 ++ Package management system locked by another process, retrying in 60s
02.24@09:28 ++ Package management system locked by another process, retrying in 60s
02.24@09:29 ++ Package management system locked by another process, retrying in 60s
02.24@09:30 ++ Package management system locked by another process, retrying in 60s
02.24@09:31 ++ Package management system locked by another process, retrying in 60s
02.24@09:32 ++ Package management system locked by another process, retrying in 60s
02.24@09:33 ++ Package management system locked by another process, retrying in 60s
02.24@09:34 ++ Package management system locked by another process, retrying in 60s
02.24@09:35 ++ Package management system locked by another process, retrying in 60s
02.24@09:36 ++ Package management system locked by another process, retrying in 60s
02.24@09:37 ++ Package management system locked by another process, retrying in 60s
02.24@09:38 ++ Package management system locked by another process, retrying in 60s
02.24@09:39 ++ Package management system locked by another process, retrying in 60s
02.24@09:40 ++ Package management system locked by another process, retrying in 60s
02.24@09:41 ++ Package management system locked by another process, retrying in 60s
02.24@09:42 ++ Package management system locked by another process, retrying in 60s
02.24@09:43 ++ Package management system locked by another process, retrying in 60s
02.24@09:44 ++ Package management system locked by another process, retrying in 60s
02.24@09:45 ++ Package management system locked by another process, retrying in 60s
02.24@09:54 ++ Package management system locked by another process, retrying in 60s
02.24@09:55 ++ Package management system locked by another process, retrying in 60s
02.24@09:56 ++ Package management system locked by another process, retrying in 60s
02.24@09:57 ++ Package management system locked by another process, retrying in 60s
02.24@09:58 ++ Package management system locked by another process, retrying in 60s
02.24@09:59 ++ Package management system locked by another process, retrying in 60s
02.24@10:00 ++ Package management system locked by another process, retrying in 60s
02.24@10:01 ++ Package management system locked by another process, retrying in 60s
02.24@10:02 ++ Package management system locked by another process, retrying in 60s
02.24@10:03 ++ Package management system locked by another process, retrying in 60s
02.24@10:04 ++ Package management system locked by another process, retrying in 60s
02.24@10:05 ++ Package management system locked by another process, retrying in 60s
02.24@10:06 ++ Package management system locked by another process, retrying in 60s
02.24@10:07 ++ Package management system locked by another process, retrying in 60s
02.24@10:08 ++ Package management system locked by another process, retrying in 60s
02.24@10:09 ++ Package management system locked by another process, retrying in 60s
02.24@10:10 ++ Package management system locked by another process, retrying in 60s
02.24@10:11 ++ Package management system locked by another process, retrying in 60s
02.24@10:12 ++ Package management system locked by another process, retrying in 60s
02.24@10:13 ++ Package management system locked by another process, retrying in 60s
02.24@10:14 ++ Package management system locked by another process, retrying in 60s
02.24@10:15 ++ Package management system locked by another process, retrying in 60s
02.24@10:16 ++ Package management system locked by another process, retrying in 60s
02.24@10:17 ++ Package management system locked by another process, retrying in 60s
02.24@10:18 ++ Package management system locked by another process, retrying in 60s
02.24@10:19 ++ Package management system locked by another process, retrying in 60s
02.24@10:20 ++ Package management system locked by another process, retrying in 60s
02.24@10:21 ++ Package management system locked by another process, retrying in 60s
02.24@10:22 ++ Package management system locked by another process, retrying in 60s
02.24@10:23 ++ Package management system locked by another process, retrying in 60s
02.24@10:24 ++ Package management system locked by another process, retrying in 60s
02.24@10:25 ++ Package management system locked by another process, retrying in 60s
02.24@10:26 ++ Package management system locked by another process, retrying in 60s
02.24@10:27 ++ Package management system locked by another process, retrying in 60s
02.24@10:28 ++ Package management system locked by another process, retrying in 60s
02.24@10:29 ++ Package management system locked by another process, retrying in 60s
02.24@10:30 ++ Package management system locked by another process, retrying in 60s
02.24@10:31 ++ Package management system locked by another process, retrying in 60s
02.24@10:33 ++ Package management system locked by another process, retrying in 60s
02.24@10:34 ++ Package management system locked by another process, retrying in 60s
02.24@10:35 ++ Package management system locked by another process, retrying in 60s
02.24@10:36 ++ Package management system locked by another process, retrying in 60s
02.24@10:37 ++ Package management system locked by another process, retrying in 60s
02.24@10:38 ++ Package management system locked by another process, retrying in 60s
02.24@10:39 ++ Package management system locked by another process, retrying in 60s
02.24@10:40 ++ Package management system locked by another process, retrying in 60s
02.24@10:41 ++ Package management system locked by another process, retrying in 60s
02.24@10:42 ++ Package management system locked by another process, retrying in 60s
02.24@10:43 ++ Package management system locked by another process, retrying in 60s
02.24@10:44 ++ Package management system locked by another process, retrying in 60s
02.24@10:45 ++ Package management system locked by another process, retrying in 60s
02.24@10:46 ++ Package management system locked by another process, retrying in 60s
02.24@10:47 ++ Package management system locked by another process, retrying in 60s
02.24@10:48 ++ Package management system locked by another process, retrying in 60s
02.24@10:49 ++ Package management system locked by another process, retrying in 60s
02.24@10:50 ++ Package management system locked by another process, retrying in 60s
02.24@10:51 ++ Package management system locked by another process, retrying in 60s
02.24@10:52 ++ Package management system locked by another process, retrying in 60s
02.24@10:53 ++ Package management system locked by another process, retrying in 60s
02.24@10:54 ++ Package management system locked by another process, retrying in 60s
02.24@10:55 ++ Package management system locked by another process, retrying in 60s
02.24@10:56 ++ Package management system locked by another process, retrying in 60s
02.24@10:57 ++ Package management system locked by another process, retrying in 60s
02.24@10:58 ++ Package management system locked by another process, retrying in 60s
02.24@10:59 ++ Package management system locked by another process, retrying in 60s
02.24@11:00 ++ Package management system locked by another process, retrying in 60s
02.24@11:01 ++ Package management system locked by another process, retrying in 60s
02.24@11:02 ++ Package management system locked by another process, retrying in 60s
02.24@11:03 ++ Package management system locked by another process, retrying in 60s
02.24@11:04 ++ Package management system locked by another process, retrying in 60s
02.24@11:05 ++ Package management system locked by another process, retrying in 60s
02.24@11:06 ++ Package management system locked by another process, retrying in 60s
02.24@11:07 ++ Package management system locked by another process, retrying in 60s
02.24@11:08 ++ Package management system locked by another process, retrying in 60s
02.24@11:09 ++ Package management system locked by another process, retrying in 60s
02.24@11:10 ++ Package management system locked by another process, retrying in 60s
02.24@11:11 ++ Package management system locked by another process, retrying in 60s
02.24@11:12 ++ Package management system locked by another process, retrying in 60s
02.24@11:13 ++ Package management system locked by another process, retrying in 60s
02.24@11:14 ++ Package management system locked by another process, retrying in 60s
02.24@11:15 ++ Package management system locked by another process, retrying in 60s
02.24@11:16 ++ Package management system locked by another process, retrying in 60s
02.24@11:17 ++ Package management system locked by another process, retrying in 60s
02.24@11:18 ++ Package management system locked by another process, retrying in 60s
02.24@11:19 ++ Package management system locked by another process, retrying in 60s
02.24@11:20 ++ Package management system locked by another process, retrying in 60s
02.24@11:21 ++ Package management system locked by another process, retrying in 60s
02.24@11:22 ++ Package management system locked by another process, retrying in 60s
02.24@11:23 ++ Package management system locked by another process, retrying in 60s
02.24@11:24 ++ Package management system locked by another process, retrying in 60s
02.24@11:25 ++ Package management system locked by another process, retrying in 60s
02.24@11:26 ++ Package management system locked by another process, retrying in 60s
02.24@11:27 ++ Package management system locked by another process, retrying in 60s
02.24@11:28 ++ Package management system locked by another process, retrying in 60s
02.24@11:29 ++ Package management system locked by another process, retrying in 60s
02.24@11:30 ++ Package management system locked by another process, retrying in 60s
02.24@11:31 ++ Package management system locked by another process, retrying in 60s
02.24@11:32 ++ Package management system locked by another process, retrying in 60s
02.24@11:33 ++ Package management system locked by another process, retrying in 60s
02.24@11:34 ++ Package management system locked by another process, retrying in 60s
02.24@11:35 ++ Package management system locked by another process, retrying in 60s
02.24@11:36 ++ Package management system locked by another process, retrying in 60s
02.24@11:37 ++ Package management system locked by another process, retrying in 60s
02.24@11:38 ++ Package management system locked by another process, retrying in 60s
02.24@11:39 ++ Package management system locked by another process, retrying in 60s
02.24@11:40 ++ Package management system locked by another process, retrying in 60s
02.24@11:41 ++ Package management system locked by another process, retrying in 60s
02.24@11:42 ++ Package management system locked by another process, retrying in 60s
02.24@11:43 ++ Package management system locked by another process, retrying in 60s
02.24@11:44 ++ Package management system locked by another process, retrying in 60s
02.24@11:45 ++ Package management system locked by another process, retrying in 60s
02.24@11:46 ++ Package management system locked by another process, retrying in 60s
02.24@11:47 ++ Package management system locked by another process, retrying in 60s
02.24@11:48 ++ Package management system locked by another process, retrying in 60s
02.24@11:49 ++ Package management system locked by another process, retrying in 60s
02.24@11:50 ++ Package management system locked by another process, retrying in 60s
02.24@11:51 ++ Package management system locked by another process, retrying in 60s
02.24@11:52 ++ Package management system locked by another process, retrying in 60s
02.24@11:53 ++ Package management system locked by another process, retrying in 60s
02.24@11:54 ++ Package management system locked by another process, retrying in 60s
02.24@11:55 ++ Package management system locked by another process, retrying in 60s
02.24@11:56 ++ Package management system locked by another process, retrying in 60s
02.24@11:57 ++ Package management system locked by another process, retrying in 60s
02.24@11:58 ++ Package management system locked by another process, retrying in 60s
02.24@11:59 ++ Package management system locked by another process, retrying in 60s
02.24@12:00 ++ Package management system locked by another process, retrying in 60s
02.24@12:01 ++ Package management system locked by another process, retrying in 60s
02.24@12:02 ++ Package management system locked by another process, retrying in 60s
02.24@12:03 ++ Package management system locked by another process, retrying in 60s
02.24@12:04 ++ Package management system locked by another process, retrying in 60s
02.24@12:05 ++ Package management system locked by another process, retrying in 60s

I removed a few repetitive lines because a message has to be in a limit of characters.

There is a Synaptic failure at @5:58

I performed a "Restart", still the older 65 was active. I performed a "Shut down", the pc didn't shut down. Only the screen flashed for one second and asked me to log in exactly like what had happened in the previous "restart". I performed another "shut down", the same thing. So there seems no way to power off the computer now.

The kernel info became like these:

https://ibb.co/9tnwjcz
https://ibb.co/Tr7P8yb

SMG · Post by **SMG** » Wed Feb 24, 2021 1:35 pm

Do you have a Timeshift snapshot of your system before this problem started?

I have the same Synaptic error message, so that does not seem to be the issue.

The issue is whatever is using the system. Do you know what happened at 7:58? It seems the system was okay for a little bit and then it went into "locked by another process" mode again.

Code: Select all

02.24@07:58 ++ Update Manager is in tray mode, performing recurring refresh
02.24@07:58 ++ Package management system locked by another process, retrying in 60s

verycd · Post by **verycd** » Wed Feb 24, 2021 1:52 pm

I did another two tests, When the log in screen appeared after a "shut down", I clicked the icon at the upper right corner of the small window for entering password. There are four options: Cinnamon (Default), Cinnamon (software rendering), Ubuntu, Ubuntu on Wayland. I didn't take the risk to choose anything other than the Cinnamon (Default). There is also a power icon on the upper right cornor of the entire screen. If I click it, there are two options: suspend and shut down. I clicked "shut down", a massage appeared, asking "Shut down. Are you sure you want to shut down the computer?". But there is nowhere to find Yes/No icons. Pressing "enter" doesn't do anything. Entering password only led to another log in.

Linux Mint Forums

[Solved] Stuck at "configuring grub-pc (amd64)"

[Solved] Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"

Re: Stuck at "configuring grub-pc (amd64)"