e2fsprogs-1.45.7

https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/
https://mirrors.edge.kernel.org/pub/...-1.45.7.tar.xz

Libgcrypt-1.9.1 has been released just now. It fixes an exploitable bug in libgcrypt-1.9.0’s hash functions.

3 members found this post helpful.

Fixed!

e2fsprogs-1.46.0:

(Add support for the new fast_commit feature. (Requires Linux version
5.10 or higher)

https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/

https://mirrors.edge.kernel.org/pub/...-1.46.0.tar.xz

1 members found this post helpful.

lilo
Warning: Unable to determine video adapter in use in the present system.
Warning: Video adapter does not support VESA BIOS extensions needed for
display of 256 colors. Boot loader will fall back to TEXT only operation.
Added Linux *
2 warnings were issued.


it just gets worse for -current no fixes for rsync and mariadb, or whatever is causing their errors, and now this...

no ack from Patrick either, perhaps he rather I not post these bugs for him, if its too much trouble I can stop wasting my time

1 members found this post helpful.

Pat most often doesn't ack, just provides fixes, which you know reading for instance this ChangeLog, but be sure he reads this thread. Bear in mind that he has 1500 packages or so to take care of just for Slackware-current and also insure that they all fit together, so he doesn't have much time to ack every bug report or request. Also taking care of a specific one may be not on top of his TODO list, presumably very huge, which doesn't mean he won't when the times come.

tl;dr: please just wait patiently and keep posting issues you find. This helps.

PS about lilo: this could very well be a limitation or bug of lilo that can't be fixed, as this project died long ago. As an aside, it's time to move to grub by default as most distribution have done, but that's another topic. And anyway having the text interface of lilo instead of a graphical one is not the end of the world as that doesn't prevent to boot.

@Ressy - If Pat and team spent their time acknowledging, they would spend that much less time doing.

But do expect that your post gets seen, so keep posting what you find.

If you think that a post of yours was missed, you could repost, once (more than that would be unhelpful.) If anybody knows that posts should never be followed up, say so, but nobody's perfect, so it is possible a post could be missed.

TKS

Hi,
This error has first only appeared since update within past 24 hours or so, it has not appeared on any update prior and I had been keeping the dev box fully updated as updated are released (or as time permits the jan 22 update was not run here until 27th hence why it took a week to spot the error and trace it down)

There is no GUI on this machine, since its the dev box that proves a working system before I actually update -current boxes in production , I'd rather have it stuffed, than breaking lots of other boxes

of course that means any security fixes dont get pushed to production leaving them at whatever risk the CVE score puts on them.

1 members found this post helpful.

Cheers, I do not like reposting stuff, ive made a few niggly mention of previous bugs in new bugs, I even do not like doing that, but most projects I have been involved with have bug trackers, apache, freepbx etc but slackwares BT seems to be this forum where you have no idea if the people who need to see it, see it.... guess time will tell.

Just encountered the same error after installing the 5.10.12 kernel and running lilo, after lilo.conf was edited, of course.
Anyone know the source of the error?

I went ahead and re-installed the Nvidia driver and everything appears to be working as it should.

I don't know what the source of the error is,but running the same kernel and getting the same lilo error. I'm running the kernel's Radeon driver, so I guess my only option will be to downgrade to 5.10.11 and see what happens. Will let you know.

1 members found this post helpful.

I found this thread. Haven't tried it yet.
https://www.linuxquestions.org/quest...8/#post5644478

Edit in: Nope. Doesn't appear to have anything to do with it.

Today was the first time I've had to edit and run lilo since installing the 5.10.11 kernel, so I wonder if any of the recent updates to -current may have caused this problem.

1 members found this post helpful.

Thanks. My lilo.conf has 'vga = normal'. At least I can boot and run without issues. Still, the cleaner, the better, right? ;-) I'll fiddle.

2 members found this post helpful.

I have the same problem with lilo and still