No Updates In Linux Mint In A While..... :\

[blackneos940]

Man, I'm like, all OVER these Forums lately....... :3 So anywho, using apt-get update, followed by apt-get upgrade, doesn't yield any Updates to Mint, the Kernel, Steam, Wine.... ANYTHING..... Mint Update Manager doesn't--- Wait, it just DID notify me..... Again. It did this earlier, too, for some OTHER updates..... Did it just suddenly fix itself.....? Well, before this, it wasn't doing ANYthing for a WHILE..... But now, it SEEMS like everything was ok....... Man, I sure hope this thing doesn't morph into DVL!..... So anyway, I'll report back if this happens again, ok.....? :3 (For a while there, I was worried about the Kernel Devs [Linus included, as he does work sometimes, TOO.....] ....)

 

[blackneos940]

Wait: I DID get this, after doing Updates in Guake.....

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  grub-common grub-pc grub-pc-bin grub2-common
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,233 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main grub-pc amd64 2.02~beta2-9ubuntu1.7 [173 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main grub-pc-bin amd64 2.02~beta2-9ubuntu1.7 [882 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main grub2-common amd64 2.02~beta2-9ubuntu1.7 [501 kB]
Get:4 http://archive.ubuntu.com/ubuntu/ trusty-updates/main grub-common amd64 2.02~beta2-9ubuntu1.7 [1,678 kB]
48% [4 grub-common 1,209 B/1,678 kB 0%]                             224 kB/s 7s
Fetched 3,233 kB in 20s (155 kB/s)                                         
Preconfiguring packages ...
(Reading database ... 283349 files and directories currently installed.)
Preparing to unpack .../grub-pc_2.02~beta2-9ubuntu1.7_amd64.deb ...
Unpacking grub-pc (2.02~beta2-9ubuntu1.7) over (2.02~beta2-9ubuntu1.6) ...
Preparing to unpack .../grub-pc-bin_2.02~beta2-9ubuntu1.7_amd64.deb ...
Unpacking grub-pc-bin (2.02~beta2-9ubuntu1.7) over (2.02~beta2-9ubuntu1.6) ...
Preparing to unpack .../grub2-common_2.02~beta2-9ubuntu1.7_amd64.deb ...
Unpacking grub2-common (2.02~beta2-9ubuntu1.7) over (2.02~beta2-9ubuntu1.6) ...
Preparing to unpack .../grub-common_2.02~beta2-9ubuntu1.7_amd64.deb ...
Unpacking grub-common (2.02~beta2-9ubuntu1.7) over (2.02~beta2-9ubuntu1.6) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for install-info (5.2.0.dfsg.1-2) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up grub-common (2.02~beta2-9ubuntu1.7) ...
Installing new version of config file /etc/grub.d/00_header ...
Setting up grub2-common (2.02~beta2-9ubuntu1.7) ...
Setting up grub-pc-bin (2.02~beta2-9ubuntu1.7) ...
Setting up grub-pc (2.02~beta2-9ubuntu1.7) ...
Installing for i386-pc platform.
Installation finished. No error reported.
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.2.0-22-generic
Found initrd image: /boot/initrd.img-4.2.0-22-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
  /dev/loop0p1: read failed after 0 of 4096 at 1581318144: Input/output error
  /dev/loop0p1: read failed after 0 of 4096 at 1581375488: Input/output error
  /dev/loop0p1: read failed after 0 of 4096 at 0: Input/output error
  /dev/loop0p1: read failed after 0 of 4096 at 4096: Input/output error
  /dev/loop0p2: read failed after 0 of 4096 at 2228224: Input/output error
  /dev/loop0p2: read failed after 0 of 4096 at 2318336: Input/output error
  /dev/loop0p2: read failed after 0 of 4096 at 0: Input/output error
  /dev/loop0p2: read failed after 0 of 4096 at 4096: Input/output error
  No volume groups found
done

Is something wrong with Grub.....? Is everything ok....?? Well, running apt-get upgrade again yields no Updates, so everything SEEMS normal..... :\

 

[Mitt Green]

Not sure, why you are worried. You could even remove memtest from /boot. In my kernels I usually disable it at all.

I sometimes spend a couple of days in Debian (Devuan) Unstable without updates; a coincidence, you know. Simply no package maintainer released a new version. Don't forget that Ubuntu uses pretty much 99% of unmodified packages from Debian Unstable, usually without such a mad package revision cycle, from what I've noticed.

 

[blackneos940]

Not sure, why you are worried. You could even remove memtest from /boot. In my kernels I usually disable it at all.

I sometimes spend a couple of days in Debian (Devuan) Unstable without updates; a coincidence, you know. Simply no package maintainer released a new version. Don't forget that Ubuntu uses pretty much 99% of unmodified packages from Debian Unstable, usually without such a mad package revision cycle, from what I've noticed.

Well, thank you for that insight, good sir!..... :3 ^^ I didn't even know that about Ubuntu's Packages, to be honest....... Anywho, I think I'll leave memtest there, as I have bad Luck when it comes to messing with the System Files....... :< But, why do you call Debian "Devuan".....? :<

 

[blackneos940]

Not sure, why you are worried. You could even remove memtest from /boot. In my kernels I usually disable it at all.

I sometimes spend a couple of days in Debian (Devuan) Unstable without updates; a coincidence, you know. Simply no package maintainer released a new version. Don't forget that Ubuntu uses pretty much 99% of unmodified packages from Debian Unstable, usually without such a mad package revision cycle, from what I've noticed.

And Happy New Year, good sir!!..... ^^

 

[Mitt Green]

But, why do you call Debian "Devuan"?

Devuan is Debian without systemd.

Happy holidays you too!