How does the Next deal with the videos and audio HTML5? #191

noloop · 2019-02-16T20:40:18Z

I'm looking for the project, it attracted me a lot, in time I'm looking for a simple and customizable browser. So I downloaded the Next, I liked it a lot, but he did not open the videos, I get the message:

"Your browser does not currently recognize any of the video formats available."

I do not know if something is wrong here or the Next can not see videos. I wonder if the Next supports videos and audios? And if Next do not support, what could be done to change that, what are the limitations.

jmercouris · 2019-02-17T00:21:42Z

hi @noloop thank you for your interest in the project! Did you make sure that you have all of the dependencies for Linux installed? Did you install from source? There are options dependencies for video codecs. A little more information about your set-up could help us debug this issue! thank you :)

noloop · 2019-02-17T00:28:01Z

I'm on Void Linux, I downloaded this link:

https://next.atlas.engineer/static/release/next-linux-gtk-webkit.tar.lz

So it is possible that some codecs are missing, which ones should I have? or is it already included in the unzipped "gnu" directory?

Ambrevar · 2019-02-17T11:02:03Z

This is a known issue with Guix and its gst-* packages. I'll get down to fix it as soon as possible.
In the mean time @noloop you can compile Next following the instructions in the developer's README.

A Void Linux package would also be neat :D

Ambrevar · 2019-05-08T18:12:30Z

This should be fixed in Next 1.2.1. Feel free to re-open if you still experience the issue.

nolanwrightdev · 2019-07-30T22:59:06Z

Just installed this browser via AUR. Getting that same error message: "Your browser does not currently recognize any of the video formats available." What dependencies might I might be missing? I have webkit2gtk installed already.

easbarba · 2019-07-30T23:14:34Z

@nolanwrightdev

AUR should install all dependencies, I dont think its the issue!

nolanwrightdev · 2019-07-31T00:13:51Z

Hm well idk then. I installed the browser via yay -S next-browser-git. Let me know if you want any details about my system.

Ambrevar · 2019-07-31T07:05:18Z

The dependencies to display HTML5 content are optional. From the PKGBUILD: ``` gst-plugins-bad (gst-plugins-bad-git) (optional) – for HTML5 audio/video gst-plugins-base (gst-plugins-base-git) (optional) – for HTML5 audio/video gst-plugins-good (gst-plugins-good-git) (optional) – for HTML5 audio/video gst-plugins-ugly (gst-plugins-ugly-git) (optional) – for HTML5 audio/video gstreamer (gstreamer-git) (optional) – for HTML5 audio/video ``` Install the above and you should be good to go!

nolanwrightdev · 2019-07-31T10:00:02Z

That did indeed solve the issue. Thanks, @Ambrevar.

noloop · 2019-11-05T15:22:47Z

next-gtk-webkit.log

The dependencies to display HTML5 content are optional. From the PKGBUILD: gst-plugins-bad (gst-plugins-bad-git) (optional) – for HTML5 audio/video gst-plugins-base (gst-plugins-base-git) (optional) – for HTML5 audio/video gst-plugins-good (gst-plugins-good-git) (optional) – for HTML5 audio/video gst-plugins-ugly (gst-plugins-ugly-git) (optional) – for HTML5 audio/video gstreamer (gstreamer-git) (optional) – for HTML5 audio/video Install the above and you should be good to go!

I did download the version 1.3.4 and I installed all packages and still can't see videos.

Ambrevar · 2019-11-05T16:22:03Z

Maybe delete ~/.cache/gstreamer-1.0 and try again. Can you see videos with Epiphany?

noloop · 2019-11-05T17:31:24Z

Maybe delete ~/.cache/gstreamer-1.0 and try again. Can you see videos with Epiphany?

I did this, and it still doesn't work. In Epiphany I can watch videos.

noloop · 2019-11-05T17:50:29Z

I try compile of the next source and i get:

unhandled condition in --disable-debugger mode, quitting

Compilation failed.
Make sure the 'xclip' binary and the 'sqlite' and 'libfixposix' development files are available on your system.
make: *** [Makefile:36: next] Error 1

I have all dependencies installed.

Ambrevar · 2019-11-05T17:51:40Z

Are you still using the Guix pack on Void Linux? I thought that Next was packaged for Void Linux these days, you could give this a try.

noloop · 2019-11-05T17:53:06Z

make-all-next-error.log

Are you still using the Guix pack on Void Linux? I thought that Next was packaged for Void Linux these days, you could give this a try.

I was, but I tried compiling the source now and it can't either.

And there is the next void-linux package available.

Ambrevar · 2019-11-05T18:41:29Z

What do you mean, either? The Void Linux package does not work? Can you share the error output you get when compiling?

noloop · 2019-11-05T18:47:01Z

What do you mean, either? The Void Linux package does not work? Can you share the error output you get when compiling?

It works, but I only discovered it after trying to compile, I searched before and don't find, but someone built the package. But now that I've tried to compile I would like to be able to do so.
make-all-next-error.log

Ambrevar · 2019-11-05T19:14:06Z

From the error output, you need to install openssl. If I recall correctly, Void Linux might have an openssl-dev which you'll need for the .so symlinks.

noloop · 2019-11-05T20:23:55Z

From the error output, you need to install openssl. If I recall correctly, Void Linux might have an openssl-dev which you'll need for the .so symlinks.

I installed openssl-devel and I try again:

make-all-next-error3.log

noloop · 2019-11-05T23:01:22Z

I cleaned up everything I could and tried again, and now it compiles, so I change my file "~/.config/next/init.lisp". And I tried to run next, and I get the same as I'm getting when running next void-linux package:

Next version 1.3.4-d3ece6a
Loading configuration from #P"/home/noloop/.config/next/init.lisp"...
 <INFO> [16:53:56] next remote.lisp (initialize-instance :after remote-interface) -
  D-Bus addresses: (#<Unix socket address: "NIL">)
Unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD "Anonymous thread" RUNNING
                                    {1005BFAF03}>:
  No server addresses left to try to open.

Backtrace for: #<SB-THREAD:THREAD "Anonymous thread" RUNNING {1005BFAF03}>
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SIMPLE-ERROR "No server addresses left to try to open." {1005E00A83}> #<unused argument> :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<SIMPLE-ERROR "No server addresses left to try to open." {1005E00A83}>)
2: (INVOKE-DEBUGGER #<SIMPLE-ERROR "No server addresses left to try to open." {1005E00A83}>)
3: (ERROR "No server addresses left to try to open.")
4: ((LAMBDA NIL :IN DBUS/PROTOCOLS:OPEN-CONNECTION))
5: (DBUS/CONVENIENCE::CALL-WITH-OPEN-BUS #<CLOSURE (LAMBDA (NEXT::BUS) :IN INITIALIZE-INSTANCE) {1005DF7D1B}> #<event base, 0 FDs monitored, using: #<epoll(4) multiplexer> {1005DF6353}> (#<DBUS/TRANSPORT-UNIX:UNIX-SERVER-ADDRESS {1005DF7BD3}>))
6: ((LAMBDA NIL :IN INITIALIZE-INSTANCE))
7: ((LAMBDA NIL :IN BORDEAUX-THREADS::BINDING-DEFAULT-SPECIALS))
8: ((FLET SB-UNIX::BODY :IN SB-THREAD::NEW-LISP-THREAD-TRAMPOLINE))
9: ((FLET "WITHOUT-INTERRUPTS-BODY-4" :IN SB-THREAD::NEW-LISP-THREAD-TRAMPOLINE))
10: ((FLET SB-THREAD::WITH-MUTEX-THUNK :IN SB-THREAD::NEW-LISP-THREAD-TRAMPOLINE))
11: ((FLET "WITHOUT-INTERRUPTS-BODY-1" :IN SB-THREAD::CALL-WITH-MUTEX))
12: (SB-THREAD::CALL-WITH-MUTEX #<CLOSURE (FLET SB-THREAD::WITH-MUTEX-THUNK :IN SB-THREAD::NEW-LISP-THREAD-TRAMPOLINE) {7F6270CC6D7B}> #<SB-THREAD:MUTEX "thread result lock" owner: #<SB-THREAD:THREAD "Anonymous thread" RUNNING {1005BFAF03}>> NIL T NIL)
13: (SB-THREAD::NEW-LISP-THREAD-TRAMPOLINE #<SB-THREAD:THREAD "Anonymous thread" RUNNING {1005BFAF03}> NIL #<CLOSURE (LAMBDA NIL :IN BORDEAUX-THREADS::BINDING-DEFAULT-SPECIALS) {1005BFAEAB}> NIL)
14: ("foreign function: call_into_lisp")
15: ("foreign function: new_thread_trampoline")

unhandled condition in --disable-debugger mode, quitting

Ambrevar · 2019-11-06T08:33:32Z

You need dbus. In particular, dbus-broker is not supported.

noloop · 2019-11-06T10:33:44Z

You need dbus. In particular, dbus-broker is not supported.

I have installed:

[*] dbus-1.12.16_1                                     Message bus system
[*] dbus-devel-1.12.16_1                               Message bus system - developmen...
[*] dbus-glib-0.110_1                                  GLib bindings for D-Bus
[*] dbus-glib-devel-0.110_1                            GLib bindings for D-Bus - devel...
[*] dbus-libs-1.12.16_1                                Message bus system - shared lib...
[*] dbus-x11-1.12.16_1                                 Message bus system - X11 support

and the dbus-daemon is started too.

Ambrevar · 2019-11-06T11:19:45Z

What's your window manager / desktop environment? Can you start next with the following? export $(dbus-launch) ; next

noloop · 2019-11-06T12:03:26Z

export $(dbus-launch) ; next

This doesn't work.

I use https://github.com/baskerville/bspwm

Ambrevar · 2019-11-06T12:10:09Z

Are you using systemd? Can you report the output of ps -U $USER | grep dbus

noloop · 2019-11-06T12:26:00Z

export $(dbus-launch) ; next

Sorry, I was wrong, yes it worked by exporting $(dbus-launch). But it was so slow that it crashed everything.

but already checked, it's my memory that is over, but there is still something that happens. When I close next and open again, I get:

Next version 1.3.4
Loading configuration from #P"/home/noloop/.config/next/init.lisp"...
 <INFO> [06:18:03] next remote.lisp (initialize-instance :after remote-interface) -
  D-Bus addresses: (#<Unix socket address: @"/tmp/dbus-Z6H3lsHHny">)
 <INFO> [06:18:03] next remote.lisp (initialize-instance :after remote-interface) -
  Bus connection name: :1.626
 <INFO> [06:18:03] next port.lisp (run-program port) -
  Current directory: /home/noloop/common-lisp/next-1.3.4/
 <INFO> [06:18:03] next port.lisp (run-program port) -
  Platform port path: /home/noloop/common-lisp/next-1.3.4/ports/gtk-webkit/next-gtk-webkit
 <INFO> [06:18:03] next port.lisp (run-program port) -
  Platform port arguments: NIL
 <INFO> [06:18:03] next port.lisp (run-program port) -
  Platform port log file: /home/noloop/.local/share/next/next-gtk-webkit.log
<ERROR> [06:18:04] next base.lisp (start fun2) -
  Could not connect to platform port: /home/noloop/common-lisp/next-1.3.4/ports/gtk-webkit/next-gtk-webkit
Make sure the platform port executable is either in the
PATH or set in you ~/.config/next/init.lisp, for instance:

     (setf +platform-port-command+
         "~/common-lisp/next/ports/gtk-webkit/next-gtk-webkit")

and I have to start over, sometimes this is repeated for more than once.

Are you using systemd?

Void-linux uses runit, not systemd.

ps -U $USER | grep dbus

 1262 ?        00:00:00 dbus-daemon
 1824 ?        00:00:00 dbus-daemon
 1839 ?        00:00:00 dbus-daemon
 1890 ?        00:00:00 dbus-daemon
 1928 ?        00:00:00 dbus-daemon
 1993 ?        00:00:00 dbus-daemon
 4418 ?        00:00:00 dbus-daemon
 6619 ?        00:00:00 dbus-daemon
 6646 ?        00:00:00 dbus-daemon
 6662 ?        00:00:00 dbus-daemon
 7373 ?        00:00:01 dbus-daemon
 7599 ?        00:00:00 dbus-daemon
 7899 ?        00:00:00 dbus-daemon
20437 ?        00:00:00 dbus-daemon
20776 ?        00:00:00 dbus-daemon

Ambrevar · 2019-11-06T14:32:20Z

If Next crashes, it is possible that a hung process is left running in the background. Make sure to kill `next` and `next-gtk-webkit` before trying again.

noloop · 2019-11-06T14:34:07Z

If Next crashes, it is possible that a hung process is left running in the background. Make sure to kill next and next-gtk-webkit before trying again.

but C-x C-c should not do that?

Ambrevar · 2019-11-06T14:58:28Z

Maybe a misunderstanding: - C-x C-c should quit Next. - In all cases, C-x C-c or not, if Next crashes the processes might not get cleaned up properly. Just make sure no Next process is running before starting it again.

noloop · 2019-11-06T15:28:37Z

In all cases, C-x C-c or not, if Next crashes the processes might not
get cleaned up properly. Just make sure no Next process is running
before starting it again.

But this occurs even when it does not crashes.

Ambrevar · 2019-11-06T16:09:53Z

What occurs? It seems that you have different issues. Can you list all the different cases?

noloop · 2019-11-06T16:14:15Z

What occurs? It seems that you have different issues. Can you list all the different cases?

No, we have all solved so far, now there is only one, that when I open Next and then close it, the next time I open it I have to try more than once to get it open.

Ambrevar · 2019-11-06T16:22:48Z

So can you check the background processes after you've quit Next? Any "next" something running?

noloop · 2019-11-06T18:16:04Z

So can you check the background processes after you've quit Next? Any "next" something running?

During next execution:

after C-x C-c:

Perhaps is the WebKitNetworkPr that doesn't should be here. But the Next should not that kill the WebKitNetworkPr?

noloop · 2019-11-06T22:26:00Z

I restarted my system and run only the Next.

Here, all way until crashes the Next. When I watch a video the Next crashes with or whitout free memory.

next.log

noloop · 2019-11-07T00:08:09Z

I downloaded the "next-pyqt-webengine" and I can watch video whitout crashes the Next and it seems to work faster. But when I try write here by example, It doesn't work the Capslook and also doesn't work the space key. And I can't write in the C-l input (minibuffer).

I see this whe I press CAPSLOOK:

WARNING:
   Method handler (NEXT::CORE-OBJECT
                   NEXT::PUSH-INPUT-EVENT) signaled an error: Method error: "Traceback (most recent call last):
  File \"site-packages/dbus/service.py\", line 707, in _message_cb
  File \"next-pyqt-webengine.py\", line 161, in generate_input_event
  File \"utility.py\", line 143, in generate_input_event
ValueError: chr() arg not in range(0x110000)
"..

Ambrevar · 2019-11-07T12:25:55Z

Indeed, it seems that Next is not closing properly on your system.
What if you kill the window instead of pressing C-x C-c?

WebKitGTK tends to crash a lot when watching videos. This is not directly a Next issue, although we could probably do better.
PyQt is experimental, it still has some issues.

noloop · 2019-11-07T12:37:35Z

I think the problem is that WebKitGTK always crashes and Next can't close properly, because with PyQt with C-x C-c it seems to kill correctly every time I try.

This is bad because the two available backends do not work.

Ambrevar · 2019-11-07T12:50:04Z

You seem to be the first one reporting this issue. There could be an issue with the WebKitGTK package on Void Linux. Maybe ask the Void Linux packagers? Could you try another distribution? Else you can build it using Guix: guix build -f build-scripts/guix.scm

noloop · 2019-11-07T12:57:06Z

In fact with WebKitGTKnow no crashes when watching videos, before it was just my memory that was over and crashes the Next, now I just can't mute sounds and skip video ads, but if i don't interact with elements of the page as buttons, the video is ok.

Ambrevar · 2019-11-07T15:04:29Z

I'm just guessing here. I can't reproduce your issue, so it's not easy to investigate on my side :) Some distributions maybe ship different version of WebKitGTK. Which version do you use to link against Next? Which one is used by Epiphany (if different)?

noloop · 2019-11-07T16:00:24Z

I understand, this doesn't is a block for me not use the Next, but l would like to find the problem. My version webkit2gtk that is used by Next and Epiphany:

webkit2gtk-2.26.0_1
webkit2gtk-devel-2.26.0_1

This is:

/usr/lib/libwebkit2gtk-4.0.so.37.39.1

noloop changed the title ~~How does the next deal with the videos and audio HTML5?~~ How does the Next deal with the videos and audio HTML5? Feb 16, 2019

Ambrevar closed this as completed May 8, 2019

jbmestelan mentioned this issue Sep 17, 2019

Video support in Next version 1.3.1 (downloaded archive) #382

Closed

vindarel added the pyqt label Nov 7, 2019

tviti mentioned this issue Nov 10, 2019

next-pyqt fixes #491

Closed

How does the Next deal with the videos and audio HTML5? #191

How does the Next deal with the videos and audio HTML5? #191

Comments

noloop commented Feb 16, 2019

jmercouris commented Feb 17, 2019

noloop commented Feb 17, 2019

Ambrevar commented Feb 17, 2019

Ambrevar commented May 8, 2019

nolanwrightdev commented Jul 30, 2019

easbarba commented Jul 30, 2019

nolanwrightdev commented Jul 31, 2019

Ambrevar commented Jul 31, 2019 via email

nolanwrightdev commented Jul 31, 2019

noloop commented Nov 5, 2019 • edited Loading

Ambrevar commented Nov 5, 2019 via email

noloop commented Nov 5, 2019

noloop commented Nov 5, 2019 • edited Loading

Ambrevar commented Nov 5, 2019 via email

noloop commented Nov 5, 2019 • edited Loading

Ambrevar commented Nov 5, 2019 via email

noloop commented Nov 5, 2019 • edited Loading

Ambrevar commented Nov 5, 2019 via email

noloop commented Nov 5, 2019 • edited Loading

noloop commented Nov 5, 2019

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019 • edited Loading

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019 • edited Loading

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019 • edited Loading

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019

Ambrevar commented Nov 6, 2019 via email

noloop commented Nov 6, 2019 • edited Loading

noloop commented Nov 6, 2019

noloop commented Nov 7, 2019 • edited Loading

Ambrevar commented Nov 7, 2019

noloop commented Nov 7, 2019

Ambrevar commented Nov 7, 2019 via email

noloop commented Nov 7, 2019 • edited Loading

Ambrevar commented Nov 7, 2019 via email

noloop commented Nov 7, 2019

noloop commented Nov 5, 2019 •

edited

Loading

noloop commented Nov 5, 2019 •

edited

Loading

noloop commented Nov 5, 2019 •

edited

Loading

noloop commented Nov 5, 2019 •

edited

Loading

noloop commented Nov 5, 2019 •

edited

Loading

noloop commented Nov 6, 2019 •

edited

Loading

noloop commented Nov 6, 2019 •

edited

Loading

noloop commented Nov 6, 2019 •

edited

Loading

noloop commented Nov 6, 2019 •

edited

Loading

noloop commented Nov 7, 2019 •

edited

Loading

noloop commented Nov 7, 2019 •

edited

Loading