Midori Browser with Gecko

[geo_c]

I would understand the possible reasoning of the Midori team: Puppy PPM is not longer dominant In Puppy design so making dotpet packages somewhat deprecated in favour of packaging such as apt and xbps. Debian based pups can now use apt, and these upstream package formats also work for DebianDogs and KL distros, meaning that Midori could become a good candidate for a lightweight forum-used browser more generally.

The other consideration is that @mikewalsh and @fredx181 provide puppy users portable versions of browsers, and Midori is one. I use Midori-portable64 everyday, it updates and runs perfectly.

As it stands, the only browsers I use are forum portables, they are easy to keep in sync across machines and OS's without creating accounts online and loggin in. They run in all the variations of forum distros.

[fredx181]

I would understand the possible reasoning of the Midori team: Puppy PPM is not longer dominant In Puppy design so making dotpet packages somewhat deprecated in favour of packaging such as apt and xbps. Debian based pups can now use apt, and these upstream package formats also work for DebianDogs and KL distros, meaning that Midori could become a good candidate for a lightweight forum-used browser more generally.

The other consideration is that @mikewalsh and @fredx181 provide puppy users portable versions of browsers, and Midori is one. I use Midori-portable64 everyday, it updates and runs perfectly.
....

Also when updated to v11.5 ? Then, for me Midori doesn't start anymore (see also earlier in this thread).

[mikewalsh]

@fredx181 / @geo_c :-

I would understand the possible reasoning of the Midori team: Puppy PPM is not longer dominant In Puppy design so making dotpet packages somewhat deprecated in favour of packaging such as apt and xbps. Debian based pups can now use apt, and these upstream package formats also work for DebianDogs and KL distros, meaning that Midori could become a good candidate for a lightweight forum-used browser more generally.

The other consideration is that @mikewalsh and @fredx181 provide puppy users portable versions of browsers, and Midori is one. I use Midori-portable64 everyday, it updates and runs perfectly.
....

Also when updated to v11.5 ? Then, for me Midori doesn't start anymore (see also earlier in this thread).

Me neither. 11.5 is STILL putting out the "Illegal instruction" error.....and the worst of it is, the error output won't even tell you what that illegal instruction IS. I've tried both tarball AND AppImage. No difference.

????

Mike.

[geo_c]

Also when updated to v11.5 ? Then, for me Midori doesn't start anymore (see also earlier in this thread).

Yes, I'm posting from v11.5 right this moment. But curiously, I forgot to use the included update script and accidentally updated it from within the browser which worked. I don't remember, but I may have went back and used the update script just be safe. But actually I'm not certain whether I did that or not.

I suppose I could dig up an old copy of it and do some tests.

edit: Yes now I remember.

I went back and ran the script to be safe and try and overwrite, but it gave the message "Up to Date" and didn't do anything, and so I left it at that. It's been working fine, no issues.

edit NUMBER 2: Maybe I should try it in dpupbw64, because I've been in running it in KL's

[geo_c]

edit: Yes now I remember.

I went back and ran the script to be safe and try and overwrite, but it gave the message "Up to Date" and didn't do anything, and so I left it at that. It's been working fine, no issues.

edit NUMBER 2: Maybe I should try it in dpupbw64, because I've been in running it in KL's

Yes v11.5 is working just fine in dpupbw64, but my dpupbw64 is version 10.0.7

NOTE: some of those warnings in the command log may be there because I'm blocking a lot of elements with Umatrix.

[fredx181]

edit: Yes now I remember.

I went back and ran the script to be safe and try and overwrite, but it gave the message "Up to Date" and didn't do anything, and so I left it at that. It's been working fine, no issues.

edit NUMBER 2: Maybe I should try it in dpupbw64, because I've been in running it in KL's

Yes v11.5 is working just fine in dpupbw64, but my dpupbw64 is version 10.0.7
...

Mmm.. very strange ... 11.5 not working for me (got (again) "illegal instruction" perhaps because I'm seen as being a criminal ), I tested on dpupbw64 version 10.0.9 .
edit later: tested v11.5 on KLV-Airedale too just now, same error ...

[greengeek]

edit: Yes now I remember.

I went back and ran the script to be safe and try and overwrite, but it gave the message "Up to Date" and didn't do anything, and so I left it at that. It's been working fine, no issues.

edit NUMBER 2: Maybe I should try it in dpupbw64, because I've been in running it in KL's

Yes v11.5 is working just fine in dpupbw64, but my dpupbw64 is version 10.0.7
...

Mmm.. very strange ... 11.5 not working for me (got (again) "illegal instruction" perhaps because I'm seen as being a criminal ), I tested on dpupbw64 version 10.0.9 .
edit later: tested v11.5 on KLV-Airedale too just now, same error ...

Could there be significant differences between the hardware of geo_c and yourself fredx181?

[fredx181]

Yes v11.5 is working just fine in dpupbw64, but my dpupbw64 is version 10.0.7
...

Mmm.. very strange ... 11.5 not working for me (got (again) "illegal instruction" perhaps because I'm seen as being a criminal ), I tested on dpupbw64 version 10.0.9 .
edit later: tested v11.5 on KLV-Airedale too just now, same error ...

Could there be significant differences between the hardware of geo_c and yourself fredx181?

Yes, thought about that, why not. Also between the hardware of geo_c and others who reported that 11.5 doesn't work.
edit: @geo_c What is it that you have and we all don't ?

[geo_c]

Mmm.. very strange ... 11.5 not working for me (got (again) "illegal instruction" perhaps because I'm seen as being a criminal ), I tested on dpupbw64 version 10.0.9 .
edit later: tested v11.5 on KLV-Airedale too just now, same error ...

Could there be significant differences between the hardware of geo_c and yourself fredx181?

Yes, thought about that, why not. Also between the hardware of geo_c and others who reported that 11.5 doesn't work.
edit: @geo_c What is it that you have and we all don't ?

I don't know, but it's maklng me curious. I did roll back to a fresh profile not that long ago. I wonder if I did something unusual that is now circumventing the error. It's got to be that since I ran an update from within the browser, it did something that the portable update mechanism isn't doing.

The only way to test I suppose is to download the v11.5 package fresh somehow, and see if it also runs. Not sure how to do that though, since I'm using your portable build.

EDiT: from what I see in my portable directory, it was downloaded originally as 11.4.3 and updated from there.
EDIT2: I have a 11.4.3 tar.gz in the directory, but from the output posted below it makes me wonder.

[geo_c]

Okay, interesting.

I just ran the version-check script in the terminal and got this output:

Code: Select all

./version-check
./version-check: line 4: 11.1.2: command not found
./version-check: line 5: 11.2: command not found
./version-check: line 6: 11.3.1: command not found
./version-check: line 7: 11.3.2: command not found

ADDED a screenshot Midori reports 11.5

[fredx181]

Thanks @geo_c it's obvious that you can run v11.5.
(as opposed to this bug report https://github.com/goastian/midori-desktop/issues/96 and what some posters here reported).
Perhaps indeed a hardware difference.

The version-check file is just a file that was created by the update script (as included in the portable version), not used by the internal midori updater or with manually extracting.

[greengeek]

As far as I can tell "illegal instruction" suggests either lack of cpu capability (ie similar to the old SSE issues) or incorrect GLIBC version.

Is it possible that 11.5 requires newer hware than most of us have, or newer software than is commonly available on recent Pups?

Maybe there is some fault with the recent Midori code that checks available GLIBC?

[muggins]

Just thought I'd mention that, after finding the latest Midori release gobbled up my RAM, simply reverting to the previous release didn't solve this
issue. I had to delete /root/.midori, and the ./Midori/profile directory, then start afresh, and now it's behaving

I owe the Midori team a big apology. Somehow, when I upgraded to 11.5, my Midori profiles must have been corrupted, and this seems to have caused
my RAM issues. I started afresh, and 11.5 is now running without any issues, posting from it now. So again to Midori team, Mea culpa.

[greengeek]

... I started afresh, and 11.5 is now running without any issues, posting from it now. So again to Midori team, Mea culpa.

@muggins - do you run as root or do you log in as a different user?
(Also - which puppy are you running 11.5 on please?)

[mikewalsh]

Can't entirely figure this one out. Even here in Fossapup64 9.5 on the big HP desktop rig, running - or trying to run! - with a brand new profile, I'm STILL getting the "illegal instruction" thing.

I'm wondering if the Midori team have followed the Pale Moon dev path, and coded the thing to require the AVX instruction set. I can't run the 'standard' Pale Moon on this rig, either - have to run a 3rd-party SSE2 compile instead - because Intel deliberately crippled these later Pentium 'Gold' CPUs by leaving the AVX instructions out when they built them.....supposedly, to better "aim" them at an intended market, and to tacitly 'encourage' folks to shell out for more expensive CPUs.

I'll have to try the current Midori build out on the E6430 Latitude I use in the front room when I keep Mama company in the evenings. It has a Core-i5, and that DOES have AVX....

I suspect this is going to start happening more and more often in future. AVX has been around for over a decade - it's not new, by any means! - but Intel crippled the Pentium Golds on purpose (they knew exactly WHAT they were doing, and WHY they were doing it). Just my bad luck I went & saddled myself with one before I knew about all this. Watch this space; I'll report back.

Mike.

[Jasper]

.

[muggins]

@Greengeek,

yes, running as root, on LxPupSc64.

[fredx181]

https://postimg.cc/XpszzVxx

Does clicking on the link work displaying an image for anyone ? (not for me, it's going in some sort of loop )

[Jasper]

@fredx181

Something wrong with their site

https://ibb.co/ccBSWf14

cpu flags

https://ibb.co/Csvc3dCC

[Wiz57]

https://postimg.cc/XpszzVxx

Does clicking on the link work displaying an image for anyone ? (not for me, it's going in some sort of loop )

NONE of Jasper's recent image postings work!

[Jasper]

Thats incorrect, I can see the images in my topic in the 'Graphics' subforum.

A Photo Tool Libre

I want to see what is in your signature

[Jasper]

I think I might have stumbled upon reason for images not being displayed.

The hosting site is including video adverts alongside the uploaded images.

My adblockers kick into action and I end up with no content to view. However, bandwith is being consumed in the background ie looping.

[mikewalsh]

@Jasper / @fredx181 :-

I think I see what's going on here. And it's nothing to do with ad-blockers, or 'looping'.

I'm getting an image if I click on the PostImages link (I've had an a/c with 'em for years anyway; it's where all my images come from) so that may be why.

However; I notice Jasper does NOT wrap the link with the 'img' tags. If you do, Jasper, it SHOULD show up.....but you're using the wrong link for that to work. You're using the very first one in the list, which ONLY takes you direct to the site. You need to use the second one, 'Direct Link', and then wrap it with the 'img' tags. If you do that, then it SHOULD display in your post (if you want it to, that is). OK?

Even if you only provide the link, so folks have to click on it, it STILL needs to be the 'Direct Link'. The first one will never do what you want, it ONLY works for PostImage a/c holders.

Years of experience with the site, mate! All these image-hosting sites have their quirks; you just need to experiment a bit to see which links work best for your use-case.

Mike.

[Jasper]

@mikewalsh

Did you see my cpu flags?

Does that help?

[mikewalsh]

Right, gang. Getting this thread back on track...

My suspicion IS confirmed.

Midori-portable will NOT run on the HP desktop rig. That's indisputable, and has been proved now on multiple occasions. This is entirely down to the Intel Pentium 'Gold' G5400 in this rig, which has been deliberately & intentionally "crippled" by Intel themselves.

I've just tried it out on the E6430 Dell Latitude I use in the front room in the evenings. Despite being several years older than the HP Pavilion, its Core-i5 has the AVX instruction set. Guess what? Yup; as suspected, it runs fine here. Which confirms what I've been thinking for a couple of weeks now; with the move to 11.5, the Astian team have upgraded their compile environment.....which now builds with the requirement for AVX to be present in the CPU.

So; for those of you who - like me - are getting the "Illegal instruction" error message upon trying to run Midori, ya now know WHY this is so. Unfortunately, this is a hardware limitation.....and no amount of software jiggery-pokery will "fix" it. No workarounds will make it run. The only fix will be a newer CPU.....which for many will mean a newer (or different) machine.

I do at least have the option to upgrade my CPU; desktops still have that advantage. A Core-i5 8500 will do exactly what I need, because it's the same-gen "Coffee Lake" architecture, just with AVX included. However, I won't be taking this rather drastic step simply for a pair of browsers that aren't even my regular "daily drivers"; I shall reserve this step for when ALL browsers start pulling this same stunt. (Probably won't be too much further down the line, but.....we'll see).

Unless Astian relent, and make a specific SSE2 build for 'non-compliant' hardware, Midori will henceforth be OFF THE MENU. Literally!

Sorry to be the bearer of bad news, but.....shit happens, I'm afraid.

Posting from Midori 11.5 on the E6430 Latitude right now.....it's still a good, lightweight browser, just unfortunate the Astian team have taken this step. But I suspect this sort of thing will be happening more frequently now, since AVX is present on ALL modern CPUs.

Mike.