Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post links to your 64bit module repos here. Repo maintainers are responsible for resolving any issues caused by their xzm's.
fulalas
DEV Team
DEV Team
Posts: 2050
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#16 by fulalas » 25 Nov 2022, 07:36

Try this one (make sure the old module is not activated):

https://www.mediafire.com/file/5tsvsq8w ... 6_64-1.xzm
9a58c698cf7e25bac26b75f1fc6ac4cf

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#17 by Rava » 25 Nov 2022, 13:50

fulalas wrote:
25 Nov 2022, 07:36
Try this one (make sure the old module is not activated):

https://www.mediafire.com/file/5tsvsq8w ... 6_64-1.xzm
9a58c698cf7e25bac26b75f1fc6ac4cf
I presume it is also with gst-plugins-bad-free ?

Added in 7 hours 8 minutes 13 seconds:
fulalas , the newest version is not working for me at all.

It says it loads a page but it never displays anything.

When started by a terminal I get these error messages and they keep coming:

Code: Select all

(WebKitWebProcess:24176): Gdk-WARNING **: 21:55:06.135: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was '177'.
  (Details: serial 191 error_code 177 request_code 153 (unknown) minor_code 21)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Cannot create EGL sharing context: error binding OpenGL API (EGL_BAD_PARAMETER)

(WebKitWebProcess:24179): Gdk-WARNING **: 21:55:06.220: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was '177'.
  (Details: serial 191 error_code 177 request_code 153 (unknown) minor_code 21)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Cannot create EGL sharing context: error binding OpenGL API (EGL_BAD_PARAMETER)

(WebKitWebProcess:24191): Gdk-WARNING **: 21:55:06.596: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was '177'.
  (Details: serial 191 error_code 177 request_code 153 (unknown) minor_code 21)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Cannot create EGL sharing context: error binding OpenGL API (EGL_BAD_PARAMETER)

(WebKitWebProcess:24212): Gdk-WARNING **: 21:55:07.205: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was '177'.
  (Details: serial 191 error_code 177 request_code 153 (unknown) minor_code 21)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Cannot create EGL sharing context: error binding OpenGL API (EGL_BAD_PARAMETER)

(WebKitWebProcess:24219): Gdk-WARNING **: 21:55:07.343: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was '177'.
  (Details: serial 191 error_code 177 request_code 153 (unknown) minor_code 21)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Cheers!
Yours Rava

fulalas
DEV Team
DEV Team
Posts: 2050
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#18 by fulalas » 25 Nov 2022, 23:50

Have you tried in AF?

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#19 by Rava » 26 Nov 2022, 04:11

fulalas wrote:
25 Nov 2022, 23:50
Have you tried in AF?
No. And I need my Email program or else booting up any Linux would be kinda pointless.

For now I use the older version (this one:)

Code: Select all

a8a05d1f0475377d9d427a20ad18540c  005-midori-9.0-webkit2gtk-2.35.1-x86_64-1+gst-plugins-bad-free.xzm
(Cave! I rename my modules. But you know which is which by its md5sum)

I will try using it wit always fresh, but for now work and RL take priority, so it might take some weeks until I have the time for testing it in AF. (I run all my Porteus in AF when it comes to no changes= cheatcode, but guess you also mean base-only, yes?)
Normally I use Palemoon so there is no real need for me for a 2nd browser. Unless I need a different one for e.g. video conferencing but for that midori would be the wrong choice, usually cromium-without-gøøgle does the trick for these special cases.
Cheers!
Yours Rava

Kulle
Warlord
Warlord
Posts: 594
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#20 by Kulle » 26 Nov 2022, 09:18

hi all,
The new version midori-9.0-webkit2gtk-2.38.2-x86_64-1.xzm works for me

Kulle
Warlord
Warlord
Posts: 594
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#21 by Kulle » 26 Nov 2022, 17:12


fulalas
DEV Team
DEV Team
Posts: 2050
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#22 by fulalas » 27 Nov 2022, 00:31

@Rava, trying in AF is not meant for normal use, just a matter of figuring out if the issue is related to your settings, which seems to be the case.

@Kulle, thanks. I like AppImage, but the Midori version is the new one, which I don't like. It uses Chromium engine and it's Electron-based, which is bad, really bad. Midori 9 is last good one, and we're lucky to be able to use it with any new version of Webkit, which is the actual soul of the browser :)

gnintilgyes
Black ninja
Black ninja
Posts: 73
Joined: 14 Sep 2022, 17:52
Distribution: Debian

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#23 by gnintilgyes » 27 Nov 2022, 07:04

:roll: Either Midori or Palemoon was eventually going to switch to Chromium base... oh no. I really wanted out of M$'s browser and "S" mode after I was able to return to Internet.

Yet I have to use Brave to tolerate Youtube better, go figure.

This Midori interested me somewhat but that interest was sort of killed because Rava showed me there was such thing as Palemoon, which was anything like the old Firefox.

BTW @fulalas a while ago I read your article about GNOME and I agree with many things you said. I'm a distro-hopper but the only thing with GNOME D.E. that I've ever used was Fedora 35 and it will remain that way.

EDIT: clarified for some people who have to translate to English, sorry for slang and assumed phrases.

fulalas
DEV Team
DEV Team
Posts: 2050
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#24 by fulalas » 27 Nov 2022, 07:13

@gnintilgyes, the nice thing about Webkit is that it's one of the 2 survivors of this sad web battle where Chromium engine is winning by far :(

Regarding GNOME, have you tried the official module for Porteus? All things considered, it feels like a miracle :magic:

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#25 by Rava » 02 Dec 2022, 11:07

fulalas wrote:
27 Nov 2022, 00:31
I like AppImage, but the Midori version is the new one, which I don't like. It uses Chromium engine and it's Electron-based, which is bad, really bad. Midori 9 is last good one, and we're lucky to be able to use it with any new version of Webkit, which is the actual soul of the browser :)
No Electron-based program for me Image , in this I stand with fulalas ...
Cheers!
Yours Rava

Kulle
Warlord
Warlord
Posts: 594
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#26 by Kulle » 02 Dec 2022, 18:57

Hi fulalas,
But why are Electron applications a priori bad?
Can you say that in general?
There are now many Electron applications.

fulalas
DEV Team
DEV Team
Posts: 2050
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#27 by fulalas » 02 Dec 2022, 22:00

It's basically a bazooka to kill an ant. Everything is super heavy and slow and resource hungry. This whole web framework trend is just bad. I go with minimalism, and that's why I use Porteus :)

User avatar
Rava
Contributor
Contributor
Posts: 5401
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.01 x86_64 + 4.0 i586
Location: Forests of Germany

Midori 9.0 browser (WebKitGtk 2.35.1 developer release)

Post#28 by Rava » 02 Dec 2022, 23:16

Kulle wrote:
02 Dec 2022, 18:57
But why are Electron applications a priori bad?
Electron (software framework): Reception - on en.wikipedia.org:
The most common criticism of Electron is that it necessitates software bloat when used for simple programs.[25] As a result, Michael Larabel has referred to the framework as "notorious among most Linux desktop users for being resource heavy, not integrating well with most desktops, and generally being despised".[26] [...]

Researchers have shown that the large feature set of Electron can be hijacked by malicious software since it is accessed through plaintext JavaScript files.[28] Those who are concerned with the fact that Electron is not always based on the newest version of Chromium have recommended progressive web applications as an alternative.[29]
(highlighting by me)
Cheers!
Yours Rava

Post Reply