Apparently there's a video widget in there. Why? Who knows...

Main problem with Mupdf is the lack of table of contents.

So after hours of screwing and prying I managed to gain access to where the CMOS battery is - removed it and tried to boot, no change, restored it, no change.

So either the battery is dead, or it's the graphics card that died, or something else.

Or I undid a vital wire/ribbon that I forgot about and didn't reconnect.

Ahh, for all those video-pdfs.

(hug)

I've searched all over hells half-acre for a good Linux pdf viewer. Best I came up with so far is Foxit, which isn't open source and (AFAIK), removed their Linux binaries quite recently. I run it in Fedora 40 (buggy) and also Win 10, though Adobe reader is slightly better on that.

Dunno about the video player stuff.

I stopped using Foxit on Windows when they started included adverts. Switched to Mupdf-based Sumatra PDF, which was lightweight and did everything I needed, but is Windows only.

The poorly named qpdfview has fewer dependencies than Okular (is only Qt instead of KDE), but depends on Cups, which I'll need to recompile to remove Avahi crap.

Now they (Foxit and Acrobat) have AI junk shoehorned into the interface.

Please elect me leader of the world so I can bestow well-deserved punishments on every arsehole involved in all this so-called "AI" crap. :@

It's probably the biggest grift since crypto.

Any news on the computer, Peter?

Not really.

I disconnected the graphics and RAM, but neither had any effect on behaviour.

Trying to get anywhere with the supposed replacement machine is roadblock after roadblock, with a few brick walls and dead-ends thrown in.

Everything sucks. Anything that seems good is a lie or a temporary illusion.

:(

Sorry to hear that. The world of fixing (trying to) a broken computer is like this most of the time. Replacing it is often doubly so. I'm sure it will all work out in the end. As you aren't at the end yet that isn't much use.